Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f965200a8f347c8602b1b387507a34a3db491b971d753c05f1c60c194ce4316

Tx prefix hash: 6a5cf1cd0dfcfeb31f2a298e37cb6fc39f700b7575fab04a953d18f14ed07cb7
Tx public key: 25b7114f4709ab9d469ecf017d7670e89d450192ae9c9eca63a35431498a70c6
Timestamp: 1765007785 Timestamp [UCT]: 2025-12-06 07:56:25 Age [y:d:h:m:s]: 00:017:16:20:56
Block: 1427556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12659 RingCT/type: yes/0
Extra: 0125b7114f4709ab9d469ecf017d7670e89d450192ae9c9eca63a35431498a70c6021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c0cc3ee6a5fb73f1474537edf0d2fe5ba9091e2bf2b19ba4da6c12690596f42 0.600000000000 1916259 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": 1427566, "vin": [ { "gen": { "height": 1427556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c0cc3ee6a5fb73f1474537edf0d2fe5ba9091e2bf2b19ba4da6c12690596f42" } } ], "extra": [ 1, 37, 183, 17, 79, 71, 9, 171, 157, 70, 158, 207, 1, 125, 118, 112, 232, 157, 69, 1, 146, 174, 156, 158, 202, 99, 163, 84, 49, 73, 138, 112, 198, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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