Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46aa25cd3304d4db06c500f1fc50087a9e51b3695cc5296ce0e7a7b13074dd87

Tx prefix hash: 84ec2b4423b48f98986b27d45fe3cd896287b0038263c5a8bf53a4b4e72bdff6
Tx public key: 66c79b2de16d4cf93bb7d9ef47377e03d7f94e26f18167f8fb0aba1a3b0a122d
Timestamp: 1765818648 Timestamp [UCT]: 2025-12-15 17:10:48 Age [y:d:h:m:s]: 00:022:19:02:10
Block: 1434282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16325 RingCT/type: yes/0
Extra: 0166c79b2de16d4cf93bb7d9ef47377e03d7f94e26f18167f8fb0aba1a3b0a122d02110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a76879c8c1e0b19c5428992fef12e9cc1ac75bbb59aa1a3544583bc767d2507 0.600000000000 1923071 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": 1434292, "vin": [ { "gen": { "height": 1434282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a76879c8c1e0b19c5428992fef12e9cc1ac75bbb59aa1a3544583bc767d2507" } } ], "extra": [ 1, 102, 199, 155, 45, 225, 109, 76, 249, 59, 183, 217, 239, 71, 55, 126, 3, 215, 249, 78, 38, 241, 129, 103, 248, 251, 10, 186, 26, 59, 10, 18, 45, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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