Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e3f8e05c003649e5ee489119d2a3e05a197080561c85c3b2bb9b9a5f32ad8d

Tx prefix hash: 13c818717db371faf995a033f401e1faa2d07b8988e75e898eb033209e546324
Tx public key: bd521236980fb82ea4cd0ab6671894c6c471a85b2dace3c44069da3c6e1d6058
Timestamp: 1761431513 Timestamp [UCT]: 2025-10-25 22:31:53 Age [y:d:h:m:s]: 00:074:18:30:02
Block: 1397927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53541 RingCT/type: yes/0
Extra: 01bd521236980fb82ea4cd0ab6671894c6c471a85b2dace3c44069da3c6e1d60580211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e254ef021fa246d4c6f75c3d06e2496c37e8d71bef49c50bbd173e0c39d55a7 0.600000000000 1886220 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": 1397937, "vin": [ { "gen": { "height": 1397927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e254ef021fa246d4c6f75c3d06e2496c37e8d71bef49c50bbd173e0c39d55a7" } } ], "extra": [ 1, 189, 82, 18, 54, 152, 15, 184, 46, 164, 205, 10, 182, 103, 24, 148, 198, 196, 113, 168, 91, 45, 172, 227, 196, 64, 105, 218, 60, 110, 29, 96, 88, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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