Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e70f33958a649c8df11efca70193adffab0eff7c9d92c2c87be37e312217fd

Tx prefix hash: 80c8a533f3d424bbadc910c30132c75e010ab7332f61f8d5305bdd376b6daa91
Tx public key: 67782d5212d090f87a44e1bf6ac8a7e33c57f3134f00142288b818055f2509c7
Timestamp: 1704243437 Timestamp [UCT]: 2024-01-03 00:57:17 Age [y:d:h:m:s]: 01:089:09:25:14
Block: 926910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325000 RingCT/type: yes/0
Extra: 0167782d5212d090f87a44e1bf6ac8a7e33c57f3134f00142288b818055f2509c7021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deb159cd7f0dd06eb5c435f6d59fd7b4026d20de2f2e2bee37de816ecb82b7e1 0.600000000000 1384710 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": 926920, "vin": [ { "gen": { "height": 926910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deb159cd7f0dd06eb5c435f6d59fd7b4026d20de2f2e2bee37de816ecb82b7e1" } } ], "extra": [ 1, 103, 120, 45, 82, 18, 208, 144, 248, 122, 68, 225, 191, 106, 200, 167, 227, 60, 87, 243, 19, 79, 0, 20, 34, 136, 184, 24, 5, 95, 37, 9, 199, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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