Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03526e9cf7e89d475b3e49bcddd4fe7a1379597da5071a962b97d0863e0c00d8

Tx prefix hash: 401a7ae801d820bb0eb430587bfd85467cb110d65b1f9c1a442a171098dadb3a
Tx public key: 3e3fe21bdd7f44761bcfc9ba08a42fa5d374b1d91847b2bd10b286d6c551acbd
Timestamp: 1697216780 Timestamp [UCT]: 2023-10-13 17:06:20 Age [y:d:h:m:s]: 01:199:08:35:09
Block: 868878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403533 RingCT/type: yes/0
Extra: 013e3fe21bdd7f44761bcfc9ba08a42fa5d374b1d91847b2bd10b286d6c551acbd02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.811047942000 dcy

stealth address amount amount idx
00: 415c7cc132fa9393b73e44b65cb7140b76b788fb159e6982ca43e7d02c4c23ae 0.811047942000 1323699 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": 868888, "vin": [ { "gen": { "height": 868878 } } ], "vout": [ { "amount": 811047942, "target": { "key": "415c7cc132fa9393b73e44b65cb7140b76b788fb159e6982ca43e7d02c4c23ae" } } ], "extra": [ 1, 62, 63, 226, 27, 221, 127, 68, 118, 27, 207, 201, 186, 8, 164, 47, 165, 211, 116, 177, 217, 24, 71, 178, 189, 16, 178, 134, 214, 197, 81, 172, 189, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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