Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fe6409e1923ae1c3955a5570fb4bb9b48f54741ff7fb3881fec691e02823926

Tx prefix hash: 20b358a02e626b13a1b1ed6ddce3c1baf38bd41fd643a241a045a453087d61eb
Tx public key: e59f1ddbcb03fcc105af3c0e5c109c5bef5e4374542fe3ea908bfd771fc2059b
Timestamp: 1751147578 Timestamp [UCT]: 2025-06-28 21:52:58 Age [y:d:h:m:s]: 00:142:11:26:06
Block: 1314784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99930 RingCT/type: yes/0
Extra: 01e59f1ddbcb03fcc105af3c0e5c109c5bef5e4374542fe3ea908bfd771fc2059b021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 681770c015fe58ee24d1ac148f3f5b8bd39132dfbbfe6055a75fe2410399f3f2 0.600000000000 1802435 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": 1314794, "vin": [ { "gen": { "height": 1314784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "681770c015fe58ee24d1ac148f3f5b8bd39132dfbbfe6055a75fe2410399f3f2" } } ], "extra": [ 1, 229, 159, 29, 219, 203, 3, 252, 193, 5, 175, 60, 14, 92, 16, 156, 91, 239, 94, 67, 116, 84, 47, 227, 234, 144, 139, 253, 119, 31, 194, 5, 155, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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