Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4c387965d8681a248203602c36c6e245c29b1449a7a4e33bcf64a55391d3b3

Tx prefix hash: a46a097b05bec463713a0582d7d535fe9878ef1848ea2d11414c1d4d72b8702a
Tx public key: a04d4593cc33b1fb19b5de503eb247ea9ce2fcc61b726628e20df83205332d47
Timestamp: 1687787608 Timestamp [UCT]: 2023-06-26 13:53:28 Age [y:d:h:m:s]: 01:356:17:49:13
Block: 790764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516040 RingCT/type: yes/0
Extra: 01a04d4593cc33b1fb19b5de503eb247ea9ce2fcc61b726628e20df83205332d470211000000074b8f5122000000000000000000

1 output(s) for total of 1.484904393000 dcy

stealth address amount amount idx
00: ae6a2f5b97b4c4e30042660c8873ce9832f02076c0ad95ce015ded4ebb63c085 1.484904393000 1241179 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": 790774, "vin": [ { "gen": { "height": 790764 } } ], "vout": [ { "amount": 1484904393, "target": { "key": "ae6a2f5b97b4c4e30042660c8873ce9832f02076c0ad95ce015ded4ebb63c085" } } ], "extra": [ 1, 160, 77, 69, 147, 204, 51, 177, 251, 25, 181, 222, 80, 62, 178, 71, 234, 156, 226, 252, 198, 27, 114, 102, 40, 226, 13, 248, 50, 5, 51, 45, 71, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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