Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ed25510dbb9575e2eb1a3fe823189f3816559c931afdb7deb5df2d6dc21ef4b

Tx prefix hash: f16c7db932d764b2d28daa4cfa246a75287668a821d4734a8b2a058fcb00d3f0
Tx public key: f4dce5e9f07d5fe86cd692c6f73a24e3be2aecea2f7c52d97e361822f341dc16
Timestamp: 1709105476 Timestamp [UCT]: 2024-02-28 07:31:16 Age [y:d:h:m:s]: 01:042:04:52:29
Block: 967245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291171 RingCT/type: yes/0
Extra: 01f4dce5e9f07d5fe86cd692c6f73a24e3be2aecea2f7c52d97e361822f341dc160211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ea6355084f650575286de27fb9835ab086e6742e81566043a6056b027cee5d0 0.600000000000 1427016 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": 967255, "vin": [ { "gen": { "height": 967245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ea6355084f650575286de27fb9835ab086e6742e81566043a6056b027cee5d0" } } ], "extra": [ 1, 244, 220, 229, 233, 240, 125, 95, 232, 108, 214, 146, 198, 247, 58, 36, 227, 190, 42, 236, 234, 47, 124, 82, 217, 126, 54, 24, 34, 243, 65, 220, 22, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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