Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d91491badfc71b7291d9981ec6d3a1f56e9adbd0ac865df4a648a99c4de92893

Tx prefix hash: e06d224bc4c25efe90ae01ab0858728f135ea464da2f89b393332b776b2a640a
Tx public key: 0708aa6e50ac708ccdde108e2cd85c703e6a3bcdec7b16987ddc4c239c5f5fd3
Timestamp: 1711554148 Timestamp [UCT]: 2024-03-27 15:42:28 Age [y:d:h:m:s]: 01:018:09:36:10
Block: 987560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274096 RingCT/type: yes/0
Extra: 010708aa6e50ac708ccdde108e2cd85c703e6a3bcdec7b16987ddc4c239c5f5fd30211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cacdab6b10278a32c99633200220c4faf7fd51eade040d935d3efa5ce6bc63a 0.600000000000 1447813 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": 987570, "vin": [ { "gen": { "height": 987560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cacdab6b10278a32c99633200220c4faf7fd51eade040d935d3efa5ce6bc63a" } } ], "extra": [ 1, 7, 8, 170, 110, 80, 172, 112, 140, 205, 222, 16, 142, 44, 216, 92, 112, 62, 106, 59, 205, 236, 123, 22, 152, 125, 220, 76, 35, 156, 95, 95, 211, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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