Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aadd205837ae5d54e9e9d79cf20cb15fe48a93841267da595de60495ab625020

Tx prefix hash: 2cfc1fe00218db75c8e71c88e84102a066dfc288473cc81aae7d078dc3872fc5
Tx public key: 1d5d4ea2a4637ee4324eb0dc3173ccd98ab992f71cf7d8e2a75726363b38528b
Timestamp: 1750339029 Timestamp [UCT]: 2025-06-19 13:17:09 Age [y:d:h:m:s]: 00:147:20:59:10
Block: 1308387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103493 RingCT/type: yes/0
Extra: 011d5d4ea2a4637ee4324eb0dc3173ccd98ab992f71cf7d8e2a75726363b38528b021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d465e7fd7aaf38bdc396d79226ee57f0d54ce418c4e95f1d960769fb04b1fe02 0.600000000000 1796000 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": 1308397, "vin": [ { "gen": { "height": 1308387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d465e7fd7aaf38bdc396d79226ee57f0d54ce418c4e95f1d960769fb04b1fe02" } } ], "extra": [ 1, 29, 93, 78, 162, 164, 99, 126, 228, 50, 78, 176, 220, 49, 115, 204, 217, 138, 185, 146, 247, 28, 247, 216, 226, 167, 87, 38, 54, 59, 56, 82, 139, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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