Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c702c8b97c0d042b7fc0c8d7da5096e2bd31eedcd6cb0915123643941f69779f

Tx prefix hash: d0e7b9598c407a0288682517028ae479272b7eb3c4f48be798cb331490af59c9
Tx public key: 3d3e8efff83700536cbd0843817e813f111d7ebd762c5d4392e133cc4c10a634
Timestamp: 1750717847 Timestamp [UCT]: 2025-06-23 22:30:47 Age [y:d:h:m:s]: 00:149:23:22:18
Block: 1311400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105115 RingCT/type: yes/0
Extra: 013d3e8efff83700536cbd0843817e813f111d7ebd762c5d4392e133cc4c10a634021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b8f79d74bf1a4aa3a6f2d9dc02c9a7f723fe3629e62d5c35d96dad6ea9e4453 0.600000000000 1799027 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": 1311410, "vin": [ { "gen": { "height": 1311400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b8f79d74bf1a4aa3a6f2d9dc02c9a7f723fe3629e62d5c35d96dad6ea9e4453" } } ], "extra": [ 1, 61, 62, 142, 255, 248, 55, 0, 83, 108, 189, 8, 67, 129, 126, 129, 63, 17, 29, 126, 189, 118, 44, 93, 67, 146, 225, 51, 204, 76, 16, 166, 52, 2, 17, 0, 0, 0, 3, 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