Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e4709ad303dbaf88218f8f803708c83c657eeac92f7b1f320007d3a02e01d20

Tx prefix hash: fc6f8f2ba2a7e2ed8ecf48edfdbf75bd07dd06188c573368bfb36e54b102aff6
Tx public key: f8da517aa42430190014cb60fce8a2cff4f4544317aeb1cc603119d9404d3a2f
Timestamp: 1703028181 Timestamp [UCT]: 2023-12-19 23:23:01 Age [y:d:h:m:s]: 01:111:01:21:15
Block: 916853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340493 RingCT/type: yes/0
Extra: 01f8da517aa42430190014cb60fce8a2cff4f4544317aeb1cc603119d9404d3a2f021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4d3f7a6e092cbb5f6dff80fb0e07e5e4ac6596d8cde82733c50e76d5e20bd6f 0.600000000000 1374415 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": 916863, "vin": [ { "gen": { "height": 916853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4d3f7a6e092cbb5f6dff80fb0e07e5e4ac6596d8cde82733c50e76d5e20bd6f" } } ], "extra": [ 1, 248, 218, 81, 122, 164, 36, 48, 25, 0, 20, 203, 96, 252, 232, 162, 207, 244, 244, 84, 67, 23, 174, 177, 204, 96, 49, 25, 217, 64, 77, 58, 47, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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