Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f74373d3de6f7a7e12d98446859bdf1ad434594300272037170e1aaaead8c1d

Tx prefix hash: e962fd5a7d9ee5ba2a1d95838af9a0b66eed05086c41d32bdba4e6fe5f939f86
Tx public key: 88e9bcd874495e34014f28be361c617b8f0a484a7fb9263799f3acb2727747ca
Timestamp: 1638213399 Timestamp [UCT]: 2021-11-29 19:16:39 Age [y:d:h:m:s]: 03:038:19:50:46
Block: 384869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806678 RingCT/type: yes/0
Extra: 0188e9bcd874495e34014f28be361c617b8f0a484a7fb9263799f3acb2727747ca021100000017536c63bb000000000000000000

1 output(s) for total of 32.566389279000 dcy

stealth address amount amount idx
00: 43d990d3ba04857b6a48fc34e57b62aacf1f7cfed2c4e623fbfbd8ff2a878533 32.566389279000 776740 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": 384879, "vin": [ { "gen": { "height": 384869 } } ], "vout": [ { "amount": 32566389279, "target": { "key": "43d990d3ba04857b6a48fc34e57b62aacf1f7cfed2c4e623fbfbd8ff2a878533" } } ], "extra": [ 1, 136, 233, 188, 216, 116, 73, 94, 52, 1, 79, 40, 190, 54, 28, 97, 123, 143, 10, 72, 74, 127, 185, 38, 55, 153, 243, 172, 178, 114, 119, 71, 202, 2, 17, 0, 0, 0, 23, 83, 108, 99, 187, 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