Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27efa0beebc62dc9313721c22df611f8e5a85dea4e5294d7072318070b854425

Tx prefix hash: fa570b2b5c471cf20dcfcd9ec7ce525103ce7bfd7e589d5edf0a36cdd2e8fc1e
Tx public key: 193ac8fa8ad98bd4743e0c8210a5c963ab10fe81fb3e7adf1c17dd831732ec80
Timestamp: 1706086311 Timestamp [UCT]: 2024-01-24 08:51:51 Age [y:d:h:m:s]: 01:081:07:24:19
Block: 942176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319215 RingCT/type: yes/0
Extra: 01193ac8fa8ad98bd4743e0c8210a5c963ab10fe81fb3e7adf1c17dd831732ec800211000000177a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2491de51698ce0d9271a1001394ff8c24923a4aacefbd21bf2e43b1a7a1877e 0.600000000000 1400342 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": 942186, "vin": [ { "gen": { "height": 942176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2491de51698ce0d9271a1001394ff8c24923a4aacefbd21bf2e43b1a7a1877e" } } ], "extra": [ 1, 25, 58, 200, 250, 138, 217, 139, 212, 116, 62, 12, 130, 16, 165, 201, 99, 171, 16, 254, 129, 251, 62, 122, 223, 28, 23, 221, 131, 23, 50, 236, 128, 2, 17, 0, 0, 0, 23, 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