Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 016f3a6a4cfb634976c0257f5ddd6e75ea4e3d043666534c8df702ba47e64dfe

Tx prefix hash: eaf6474816f78e9fb2d9ff33440eceb8d2ca4bdfa92b04c820b075f4a95a498d
Tx public key: 4674592e9e1d96fbdfefb99c108c3f4ed4460d549d1c682f191aae30e3bc59d5
Timestamp: 1715076384 Timestamp [UCT]: 2024-05-07 10:06:24 Age [y:d:h:m:s]: 00:239:04:39:19
Block: 1016742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171195 RingCT/type: yes/0
Extra: 014674592e9e1d96fbdfefb99c108c3f4ed4460d549d1c682f191aae30e3bc59d502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db610b56d763d9ccad64a284bf1a41e1c0c20b875737531521cfa77e7ddb4c5d 0.600000000000 1480411 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": 1016752, "vin": [ { "gen": { "height": 1016742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db610b56d763d9ccad64a284bf1a41e1c0c20b875737531521cfa77e7ddb4c5d" } } ], "extra": [ 1, 70, 116, 89, 46, 158, 29, 150, 251, 223, 239, 185, 156, 16, 140, 63, 78, 212, 70, 13, 84, 157, 28, 104, 47, 25, 26, 174, 48, 227, 188, 89, 213, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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