Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cd9a9ad79ab3d5dafc93b7cd99c1ec0ca1b7308c8d794cb391799bc3d520d2f

Tx prefix hash: dcd83f913e308b0747619dfbb2d53b25aa59af4e648e2ae7f09952424ed76eeb
Tx public key: edb326a44041f727d34f7745cfdccb0d05a987b5cfcbf14174858de54b11a736
Timestamp: 1763404344 Timestamp [UCT]: 2025-11-17 18:32:24 Age [y:d:h:m:s]: 00:038:02:34:07
Block: 1414268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27282 RingCT/type: yes/0
Extra: 01edb326a44041f727d34f7745cfdccb0d05a987b5cfcbf14174858de54b11a736021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c5a094714f476a4f46a66de0be50b3d4f1384f8419369b91c2349140dc036f 0.600000000000 1902755 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": 1414278, "vin": [ { "gen": { "height": 1414268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c5a094714f476a4f46a66de0be50b3d4f1384f8419369b91c2349140dc036f" } } ], "extra": [ 1, 237, 179, 38, 164, 64, 65, 247, 39, 211, 79, 119, 69, 207, 220, 203, 13, 5, 169, 135, 181, 207, 203, 241, 65, 116, 133, 141, 229, 75, 17, 167, 54, 2, 17, 0, 0, 0, 1, 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