Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01c9de3be28456a37c22e041b6cb5bd155cd958f0a04e455505d3d762388f94c

Tx prefix hash: cb61dc19bae704d47926a20e279744ee5b21b6aa7e7b1545ebc3f9873323782f
Tx public key: 42c27f9d8b9e5c6bf99b195fe5fe8bd2d97992b1c0a385dd02eed6db5610ed1c
Timestamp: 1632185471 Timestamp [UCT]: 2021-09-21 00:51:11 Age [y:d:h:m:s]: 03:208:14:27:14
Block: 337879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 924914 RingCT/type: yes/0
Extra: 0142c27f9d8b9e5c6bf99b195fe5fe8bd2d97992b1c0a385dd02eed6db5610ed1c02110000004bf60c5d7e000000000000000000

1 output(s) for total of 46.609516241000 dcy

stealth address amount amount idx
00: 7d4d6d7253d1e9a21fa15f6adee1823181eebe0a573e02dbe76105207a60ec8e 46.609516241000 695584 of 0

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": 337889, "vin": [ { "gen": { "height": 337879 } } ], "vout": [ { "amount": 46609516241, "target": { "key": "7d4d6d7253d1e9a21fa15f6adee1823181eebe0a573e02dbe76105207a60ec8e" } } ], "extra": [ 1, 66, 194, 127, 157, 139, 158, 92, 107, 249, 155, 25, 95, 229, 254, 139, 210, 217, 121, 146, 177, 192, 163, 133, 221, 2, 238, 214, 219, 86, 16, 237, 28, 2, 17, 0, 0, 0, 75, 246, 12, 93, 126, 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