Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 596ab64ec6b499987a7fb0ff8474104b643c73cee05188a319d3c8a4635e5489

Tx prefix hash: f91a0a441ec2fbb4e26d150771adeee0abfc6378c921d8d6b856f752e98ea95b
Tx public key: 17ac1b03aa46dc911003690dcde95ffd85dc7c32ea46276d5ba7bca3cb2fdbf3
Timestamp: 1703014199 Timestamp [UCT]: 2023-12-19 19:29:59 Age [y:d:h:m:s]: 01:335:14:08:18
Block: 916739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498693 RingCT/type: yes/0
Extra: 0117ac1b03aa46dc911003690dcde95ffd85dc7c32ea46276d5ba7bca3cb2fdbf3021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f4ecff45c78599f86d091ea2eea3677da7feeb457e31e0c70eadd6f8e1f9a29 0.600000000000 1374299 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": 916749, "vin": [ { "gen": { "height": 916739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f4ecff45c78599f86d091ea2eea3677da7feeb457e31e0c70eadd6f8e1f9a29" } } ], "extra": [ 1, 23, 172, 27, 3, 170, 70, 220, 145, 16, 3, 105, 13, 205, 233, 95, 253, 133, 220, 124, 50, 234, 70, 39, 109, 91, 167, 188, 163, 203, 47, 219, 243, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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