Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e36e87341a6bc1a2b3767c5cb1ed8351cf124832abe3639a1b82ea093f75d1ce

Tx prefix hash: 9b532abbc9e010afc23db357dfeababa86b994df8b922502f347bf754417ec6d
Tx public key: ca98c387feaa249ef735554151fba6e9f82fa2ec9eabc804f071ff2b2736e98e
Timestamp: 1754512902 Timestamp [UCT]: 2025-08-06 20:41:42 Age [y:d:h:m:s]: 00:014:21:51:39
Block: 1341697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9751 RingCT/type: yes/0
Extra: 01ca98c387feaa249ef735554151fba6e9f82fa2ec9eabc804f071ff2b2736e98e021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db528044fafce66c3ba9787e417a6ae2df30106c59eb59e66fd70cbf53fa3c7 0.600000000000 1829524 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": 1341707, "vin": [ { "gen": { "height": 1341697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db528044fafce66c3ba9787e417a6ae2df30106c59eb59e66fd70cbf53fa3c7" } } ], "extra": [ 1, 202, 152, 195, 135, 254, 170, 36, 158, 247, 53, 85, 65, 81, 251, 166, 233, 248, 47, 162, 236, 158, 171, 200, 4, 240, 113, 255, 43, 39, 54, 233, 142, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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