Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac20263ba0c1b705fe021f957ee92575657cff34f05e5140e5bf4cb9b8801c1e

Tx prefix hash: a5a6349185dab1061cb568bc89fcffd49e4b7364b79f0085b8e8f3a854c5bbc1
Tx public key: b06093cc7f2c135274fd62bb031feb4660a8e07e89e23c00dca895e79d6cec64
Timestamp: 1720173992 Timestamp [UCT]: 2024-07-05 10:06:32 Age [y:d:h:m:s]: 00:252:14:45:50
Block: 1058994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180497 RingCT/type: yes/0
Extra: 01b06093cc7f2c135274fd62bb031feb4660a8e07e89e23c00dca895e79d6cec640211000000127a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de949508ceba3e38731fe5ddf0f3d37ed548baa06019479e5df81b1df1b105f1 0.600000000000 1529453 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": 1059004, "vin": [ { "gen": { "height": 1058994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de949508ceba3e38731fe5ddf0f3d37ed548baa06019479e5df81b1df1b105f1" } } ], "extra": [ 1, 176, 96, 147, 204, 127, 44, 19, 82, 116, 253, 98, 187, 3, 31, 235, 70, 96, 168, 224, 126, 137, 226, 60, 0, 220, 168, 149, 231, 157, 108, 236, 100, 2, 17, 0, 0, 0, 18, 122, 156, 244, 199, 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