Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 37e9c3409d005e061a244e95b121ad12afa68127f04db1b8b24354cd4e0e6814

Tx prefix hash: 31d8cce468042b650f29d0525bcc4f52bd5e72a482f8bf854863badc493c0a87
Tx public key: a6cced9524345fdbd97c0d0df27ba4031e8b5910301e7b4303dacde2fd4b4604
Timestamp: 1721092876 Timestamp [UCT]: 2024-07-16 01:21:16 Age [y:d:h:m:s]: 00:274:20:58:55
Block: 1066632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196367 RingCT/type: yes/0
Extra: 01a6cced9524345fdbd97c0d0df27ba4031e8b5910301e7b4303dacde2fd4b4604021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86f331c47ff5bd972fc11be42fc9c179653f3c13c64a3d8c2eb9a3adf545975a 0.600000000000 1537299 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1066642, "vin": [ { "gen": { "height": 1066632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86f331c47ff5bd972fc11be42fc9c179653f3c13c64a3d8c2eb9a3adf545975a" } } ], "extra": [ 1, 166, 204, 237, 149, 36, 52, 95, 219, 217, 124, 13, 13, 242, 123, 164, 3, 30, 139, 89, 16, 48, 30, 123, 67, 3, 218, 205, 226, 253, 75, 70, 4, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8