Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57a4808877c5165fe19c7cde43db21f106c954998b137f8e8c6a5d10b4f13121

Tx prefix hash: 22222ad0e8040d9e6f664724729823c76d28152fc5a2fd59a1c5df53cade90d3
Tx public key: 8fee5f6d7f1a387659579b1da5e7f45c48743b8269d69cf621af32a91303a960
Timestamp: 1714838687 Timestamp [UCT]: 2024-05-04 16:04:47 Age [y:d:h:m:s]: 00:249:20:56:33
Block: 1014776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178836 RingCT/type: yes/0
Extra: 018fee5f6d7f1a387659579b1da5e7f45c48743b8269d69cf621af32a91303a9600211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0848a015d92466e95bbf01e9b234c6adc1d0af12c83e66f914d3d44f270dac1d 0.600000000000 1477959 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": 1014786, "vin": [ { "gen": { "height": 1014776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0848a015d92466e95bbf01e9b234c6adc1d0af12c83e66f914d3d44f270dac1d" } } ], "extra": [ 1, 143, 238, 95, 109, 127, 26, 56, 118, 89, 87, 155, 29, 165, 231, 244, 92, 72, 116, 59, 130, 105, 214, 156, 246, 33, 175, 50, 169, 19, 3, 169, 96, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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