Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c040e20320ecfa7981357f5280692b346dddc8f3f71bfa938a2a4c6a37f6af15

Tx prefix hash: e17440a3e6224189adae19f55a40066a65e3f862fb2f841cea08dac5aa00115f
Tx public key: 8782041bfe71b8b15ac3fa5b8bcf0823d827fdcef5c3e03664a3c722b9f3aee6
Timestamp: 1729325790 Timestamp [UCT]: 2024-10-19 08:16:30 Age [y:d:h:m:s]: 00:208:12:26:35
Block: 1134860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148833 RingCT/type: yes/0
Extra: 018782041bfe71b8b15ac3fa5b8bcf0823d827fdcef5c3e03664a3c722b9f3aee60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c80f374f1abc7e940aeaf1f2c4b6b8882ed7d24d644c70ae22d57239e1450e4d 0.600000000000 1618187 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": 1134870, "vin": [ { "gen": { "height": 1134860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c80f374f1abc7e940aeaf1f2c4b6b8882ed7d24d644c70ae22d57239e1450e4d" } } ], "extra": [ 1, 135, 130, 4, 27, 254, 113, 184, 177, 90, 195, 250, 91, 139, 207, 8, 35, 216, 39, 253, 206, 245, 195, 224, 54, 100, 163, 199, 34, 185, 243, 174, 230, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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