Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c400f693724dc49a7e86e10ef11144daccc150853e300430a34065cf94210a12

Tx prefix hash: 6b5b68e1a91679c416fe7fdb24f9e0868cf7836a0e2a3326fc47d8eb5c071630
Tx public key: 68ce6410b4cbfa2f2c4dfaaf97bc6343f7a11f77ae67dece3dccee37b2ab6c64
Timestamp: 1722878076 Timestamp [UCT]: 2024-08-05 17:14:36 Age [y:d:h:m:s]: 00:144:15:14:52
Block: 1081420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103472 RingCT/type: yes/0
Extra: 0168ce6410b4cbfa2f2c4dfaaf97bc6343f7a11f77ae67dece3dccee37b2ab6c6402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab56ff916e365c9ca3df7c3227e6fad719e92a7bd4077ace0b0c85fce6344990 0.600000000000 1555155 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": 1081430, "vin": [ { "gen": { "height": 1081420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab56ff916e365c9ca3df7c3227e6fad719e92a7bd4077ace0b0c85fce6344990" } } ], "extra": [ 1, 104, 206, 100, 16, 180, 203, 250, 47, 44, 77, 250, 175, 151, 188, 99, 67, 247, 161, 31, 119, 174, 103, 222, 206, 61, 204, 238, 55, 178, 171, 108, 100, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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