Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abeb354bc6103f0f83e92ecb3a6818e093799f3ec4a252dd0938685dab8c015f

Tx prefix hash: f887bb09c50600fdccf3edc3adf2a154cb89341d1ea22f580f78f969e21cb68f
Tx public key: 7d16653474ba344d8c482bc229f628b626c17e226b10f74b14465776d29afe50
Timestamp: 1722930963 Timestamp [UCT]: 2024-08-06 07:56:03 Age [y:d:h:m:s]: 01:094:08:59:22
Block: 1081847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325931 RingCT/type: yes/0
Extra: 017d16653474ba344d8c482bc229f628b626c17e226b10f74b14465776d29afe50021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3113c99a0390ea1df8630d26a44e85f8508f5daceba308fcf292a7d3a6bfef4 0.600000000000 1555670 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": 1081857, "vin": [ { "gen": { "height": 1081847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3113c99a0390ea1df8630d26a44e85f8508f5daceba308fcf292a7d3a6bfef4" } } ], "extra": [ 1, 125, 22, 101, 52, 116, 186, 52, 77, 140, 72, 43, 194, 41, 246, 40, 182, 38, 193, 126, 34, 107, 16, 247, 75, 20, 70, 87, 118, 210, 154, 254, 80, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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