Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f224630c0489b72946760d6a29e85c8d7dfcaa815e11d62170c6f6f2bdf845b

Tx prefix hash: e51557e7fcc9c3f5c07191dfcdb1944b814962088d0b96d451433247f58d373b
Tx public key: 5903c50ccac0051cb51addb39b15078033e9b374b31b0525d4b5539c41de60eb
Timestamp: 1765862020 Timestamp [UCT]: 2025-12-16 05:13:40 Age [y:d:h:m:s]: 00:020:18:34:35
Block: 1434638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14896 RingCT/type: yes/0
Extra: 015903c50ccac0051cb51addb39b15078033e9b374b31b0525d4b5539c41de60eb021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89b9f13b75f3f6f30a298f76ff26e9f6a424e4a73b6d17306b48e59e91555cf6 0.600000000000 1923429 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": 1434648, "vin": [ { "gen": { "height": 1434638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89b9f13b75f3f6f30a298f76ff26e9f6a424e4a73b6d17306b48e59e91555cf6" } } ], "extra": [ 1, 89, 3, 197, 12, 202, 192, 5, 28, 181, 26, 221, 179, 155, 21, 7, 128, 51, 233, 179, 116, 179, 27, 5, 37, 212, 181, 83, 156, 65, 222, 96, 235, 2, 17, 0, 0, 0, 7, 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