Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28e1c3c5bfc8816364c741cff3f6e1967d1f023fe59f77637640607d5937b059

Tx prefix hash: 3a6459140b77d2ecdbb29a4f25d0afe8cb3601225e98e3f8b5a72817e9e93ff7
Tx public key: ba9d5399f7cfd0b144a1431c0bd776e70c1722d3b17874a7feb38155e14da67a
Timestamp: 1714491495 Timestamp [UCT]: 2024-04-30 15:38:15 Age [y:d:h:m:s]: 01:030:20:51:04
Block: 1011885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283033 RingCT/type: yes/0
Extra: 01ba9d5399f7cfd0b144a1431c0bd776e70c1722d3b17874a7feb38155e14da67a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deaf4cbf41c04bac34eee3500e24869d1d4b0c1eca411b742c04d395520f26f7 0.600000000000 1474239 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": 1011895, "vin": [ { "gen": { "height": 1011885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deaf4cbf41c04bac34eee3500e24869d1d4b0c1eca411b742c04d395520f26f7" } } ], "extra": [ 1, 186, 157, 83, 153, 247, 207, 208, 177, 68, 161, 67, 28, 11, 215, 118, 231, 12, 23, 34, 211, 177, 120, 116, 167, 254, 179, 129, 85, 225, 77, 166, 122, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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