Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb3e5ade3ff3a299623fc0b914552c1867ca11e0804cbe43ffd506e0ed71874e

Tx prefix hash: 25a0c19341c3eefcbd4d337c95f15856b9388fc8b0d80a5f898db2830544a2ba
Tx public key: 36f8371f65f411036c2b64999b4c374da7e69831a443921a30b3ddd4ef5d2f35
Timestamp: 1764581801 Timestamp [UCT]: 2025-12-01 09:36:41 Age [y:d:h:m:s]: 00:003:03:57:58
Block: 1424029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2286 RingCT/type: yes/0
Extra: 0136f8371f65f411036c2b64999b4c374da7e69831a443921a30b3ddd4ef5d2f35021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a613fb3d66543eea69a144736c19a2b41676cccb67a6ccf35385546a9bbaf0e6 0.600000000000 1912658 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": 1424039, "vin": [ { "gen": { "height": 1424029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a613fb3d66543eea69a144736c19a2b41676cccb67a6ccf35385546a9bbaf0e6" } } ], "extra": [ 1, 54, 248, 55, 31, 101, 244, 17, 3, 108, 43, 100, 153, 155, 76, 55, 77, 167, 230, 152, 49, 164, 67, 146, 26, 48, 179, 221, 212, 239, 93, 47, 53, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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