Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee6bcffa75440a1cc9ca98a2afa8005aae9272b357bd69070d3fa876b174204b

Tx prefix hash: fc043d801ca05d22c9923a87595b37fa6c38f492b0d0dc20f8512453b1e5dc66
Tx public key: 0f0d1d29bfd29157d60293439384279b0c8a28c9fab4a708285ec7e3f81cbf7f
Timestamp: 1721963254 Timestamp [UCT]: 2024-07-26 03:07:34 Age [y:d:h:m:s]: 00:257:08:39:14
Block: 1073830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183855 RingCT/type: yes/0
Extra: 010f0d1d29bfd29157d60293439384279b0c8a28c9fab4a708285ec7e3f81cbf7f02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcbb6ba402f8324e0c60838182f25e315d5a4229ea0b277ce0af078988d768c7 0.600000000000 1546337 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": 1073840, "vin": [ { "gen": { "height": 1073830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcbb6ba402f8324e0c60838182f25e315d5a4229ea0b277ce0af078988d768c7" } } ], "extra": [ 1, 15, 13, 29, 41, 191, 210, 145, 87, 214, 2, 147, 67, 147, 132, 39, 155, 12, 138, 40, 201, 250, 180, 167, 8, 40, 94, 199, 227, 248, 28, 191, 127, 2, 17, 0, 0, 0, 14, 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