Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ee8f917871b24da0c07a7bfe89979a57dde8ba5d451bf5b438538aefd743b5

Tx prefix hash: 5292d519a2c126003cde98215c5fe25bec0dad5f736e238bc53292687613f05b
Tx public key: b197fdd6bec7c6b1c358986c30738e5c623f29a5907f73e2167a6227ed9011c0
Timestamp: 1723798588 Timestamp [UCT]: 2024-08-16 08:56:28 Age [y:d:h:m:s]: 00:215:01:57:19
Block: 1089042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153616 RingCT/type: yes/0
Extra: 01b197fdd6bec7c6b1c358986c30738e5c623f29a5907f73e2167a6227ed9011c0021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f42e6600673c2f67855fa5fc59638263dd5f519d16a3c4cd87f0b9f5e623f8ea 0.600000000000 1563661 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": 1089052, "vin": [ { "gen": { "height": 1089042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f42e6600673c2f67855fa5fc59638263dd5f519d16a3c4cd87f0b9f5e623f8ea" } } ], "extra": [ 1, 177, 151, 253, 214, 190, 199, 198, 177, 195, 88, 152, 108, 48, 115, 142, 92, 98, 63, 41, 165, 144, 127, 115, 226, 22, 122, 98, 39, 237, 144, 17, 192, 2, 17, 0, 0, 0, 1, 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