Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ca05b57ed1704e9455fc12f42c437cf036c5fc12c98f5863d755b283fb2a956

Tx prefix hash: 901a471c681e236bc68899633cbb815664c7274c17b4ab56ca3d28814947d7c7
Tx public key: cdc161540d4a91d5768c793bcc7d2b9e914abb2baa56a9ab39c643c8b6630b7f
Timestamp: 1763685237 Timestamp [UCT]: 2025-11-21 00:33:57 Age [y:d:h:m:s]: 00:007:05:48:33
Block: 1416584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5202 RingCT/type: yes/0
Extra: 01cdc161540d4a91d5768c793bcc7d2b9e914abb2baa56a9ab39c643c8b6630b7f02110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7de4e918a1bc4292a3b8416268c43853ce8abfff7d69c4f6d71da56ce42a185 0.600000000000 1905103 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": 1416594, "vin": [ { "gen": { "height": 1416584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7de4e918a1bc4292a3b8416268c43853ce8abfff7d69c4f6d71da56ce42a185" } } ], "extra": [ 1, 205, 193, 97, 84, 13, 74, 145, 213, 118, 140, 121, 59, 204, 125, 43, 158, 145, 74, 187, 43, 170, 86, 169, 171, 57, 198, 67, 200, 182, 99, 11, 127, 2, 17, 0, 0, 0, 2, 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