Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c20fa4c84b869be1206360df87a7b355a75cde5143461ab8b1ab2009425a187f

Tx prefix hash: 1e471d330328a8e4cbf274e6f68d79da45c07506d129407f4ec29f727fd4626f
Tx public key: 339528474f783f7e28515602be50f7affc314cca7ad1e80a1ac0879c6c2f3e52
Timestamp: 1711904067 Timestamp [UCT]: 2024-03-31 16:54:27 Age [y:d:h:m:s]: 01:221:18:29:38
Block: 990448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417161 RingCT/type: yes/0
Extra: 01339528474f783f7e28515602be50f7affc314cca7ad1e80a1ac0879c6c2f3e520211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e01242d1c10aa05b0ee49de7e4b1cf81636c04b5f81b891fb7aa80b4bda312d 0.600000000000 1450770 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": 990458, "vin": [ { "gen": { "height": 990448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e01242d1c10aa05b0ee49de7e4b1cf81636c04b5f81b891fb7aa80b4bda312d" } } ], "extra": [ 1, 51, 149, 40, 71, 79, 120, 63, 126, 40, 81, 86, 2, 190, 80, 247, 175, 252, 49, 76, 202, 122, 209, 232, 10, 26, 192, 135, 156, 108, 47, 62, 82, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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