Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3a665c5dfaaad851de07cb21c1fad9cae32fdb4aa9770439872e62a37f5476f

Tx prefix hash: 6998e089b602a73e835093fb98717a000553e2f09749fba0e4a17bcd7d3b65f3
Tx public key: e59c5bf9f40e65e644c0aa62bab930c38b5f0cb2426c8ef2ba42602b8afec120
Timestamp: 1583237480 Timestamp [UCT]: 2020-03-03 12:11:20 Age [y:d:h:m:s]: 04:091:00:36:40
Block: 75513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 959220 RingCT/type: yes/0
Extra: 01e59c5bf9f40e65e644c0aa62bab930c38b5f0cb2426c8ef2ba42602b8afec1200211000001b97adf42d3000000000000000000

1 output(s) for total of 344.980764743000 dcy

stealth address amount amount idx
00: 17f0213c221e9c4e748747a5ae4c4f4ae412ab515f9ca8b22f3547e086f29578 344.980764743000 139461 of 0

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": 75523, "vin": [ { "gen": { "height": 75513 } } ], "vout": [ { "amount": 344980764743, "target": { "key": "17f0213c221e9c4e748747a5ae4c4f4ae412ab515f9ca8b22f3547e086f29578" } } ], "extra": [ 1, 229, 156, 91, 249, 244, 14, 101, 230, 68, 192, 170, 98, 186, 185, 48, 195, 139, 95, 12, 178, 66, 108, 142, 242, 186, 66, 96, 43, 138, 254, 193, 32, 2, 17, 0, 0, 1, 185, 122, 223, 66, 211, 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