Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 049d7b169aa9a334e6378056ed37c5f38dc331deb79d93636de4aec829de530d

Tx prefix hash: 22adad467a37abb3d4fd5e39d76fe827a4b370fbd5da8f3fdd3fc05b9cf17ecd
Tx public key: 9c9e8c3b876c0c0dbd79a1d91c24cf3ed9c7d8a4da949a624fde05d84502ab4f
Timestamp: 1720648806 Timestamp [UCT]: 2024-07-10 22:00:06 Age [y:d:h:m:s]: 00:266:05:35:50
Block: 1062939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190192 RingCT/type: yes/0
Extra: 019c9e8c3b876c0c0dbd79a1d91c24cf3ed9c7d8a4da949a624fde05d84502ab4f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e126b106d9a15b4cd84af1fc4adf56e50092bb0b0a7e76a5402ab2eb7507f1d 0.600000000000 1533450 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": 1062949, "vin": [ { "gen": { "height": 1062939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e126b106d9a15b4cd84af1fc4adf56e50092bb0b0a7e76a5402ab2eb7507f1d" } } ], "extra": [ 1, 156, 158, 140, 59, 135, 108, 12, 13, 189, 121, 161, 217, 28, 36, 207, 62, 217, 199, 216, 164, 218, 148, 154, 98, 79, 222, 5, 216, 69, 2, 171, 79, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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