Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0e8a689f3d9108fa2bf809888f871ed4a465cfde65350dd6c759d641a1fd1c

Tx prefix hash: 0c7fc4d581c53b4dbadae1cb54c145a771b1d188d8284d7a01c7e447cc5a9cf1
Tx public key: b8f5df02601443ba8b9929811eda17be75d67a3c475b88f02cbb7e3e53e1db91
Timestamp: 1745006641 Timestamp [UCT]: 2025-04-18 20:04:01 Age [y:d:h:m:s]: 00:283:16:11:05
Block: 1264365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200373 RingCT/type: yes/0
Extra: 01b8f5df02601443ba8b9929811eda17be75d67a3c475b88f02cbb7e3e53e1db91021100000013dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 229c1388fffeff32add2e87f1bb8870bc554f1477fc21534c73629acac9055b4 0.600000000000 1751562 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": 1264375, "vin": [ { "gen": { "height": 1264365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "229c1388fffeff32add2e87f1bb8870bc554f1477fc21534c73629acac9055b4" } } ], "extra": [ 1, 184, 245, 223, 2, 96, 20, 67, 186, 139, 153, 41, 129, 30, 218, 23, 190, 117, 214, 122, 60, 71, 91, 136, 240, 44, 187, 126, 62, 83, 225, 219, 145, 2, 17, 0, 0, 0, 19, 219, 181, 113, 193, 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