Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d60cc16d243c071c150e83e183408ff8c403a81673c270aa79381cb4fa8af30

Tx prefix hash: 8b316b38e65a2a8d7409e70457911f740e6908c1fc14230242e46d7f6c22d9a9
Tx public key: 2cdb9da653c95ab3192aa02fc551f0b0b8a11ebe03595a4262a2300d30198d60
Timestamp: 1762155379 Timestamp [UCT]: 2025-11-03 07:36:19 Age [y:d:h:m:s]: 00:090:20:37:55
Block: 1403914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64882 RingCT/type: yes/0
Extra: 012cdb9da653c95ab3192aa02fc551f0b0b8a11ebe03595a4262a2300d30198d60021100000008df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ff7a573ee8ae1ceb58e5f14a09344a7ce697b5949250db46c5b1655425e4d38 0.600000000000 1892267 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": 1403924, "vin": [ { "gen": { "height": 1403914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ff7a573ee8ae1ceb58e5f14a09344a7ce697b5949250db46c5b1655425e4d38" } } ], "extra": [ 1, 44, 219, 157, 166, 83, 201, 90, 179, 25, 42, 160, 47, 197, 81, 240, 176, 184, 161, 30, 190, 3, 89, 90, 66, 98, 162, 48, 13, 48, 25, 141, 96, 2, 17, 0, 0, 0, 8, 223, 90, 36, 122, 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