Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 840bd600eb14a04e4b27e1b47769224057f83bd302ae20c5517c11ae61c05476

Tx prefix hash: 483d70bcb533ec1b45524602c7a19dce5c0dc0a4ef6f12b710890588d2ac168a
Tx public key: 25f844170d9b9d3f6bc318340b967483f86275a2dad58b3ebdf60d9817c69a99
Timestamp: 1736374224 Timestamp [UCT]: 2025-01-08 22:10:24 Age [y:d:h:m:s]: 00:162:18:13:29
Block: 1193168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115994 RingCT/type: yes/0
Extra: 0125f844170d9b9d3f6bc318340b967483f86275a2dad58b3ebdf60d9817c69a9902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b09c416b03f9d9a61f14935d238884d1281ebd1c1343c6c493820ca9bcdb2c09 0.600000000000 1679727 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": 1193178, "vin": [ { "gen": { "height": 1193168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b09c416b03f9d9a61f14935d238884d1281ebd1c1343c6c493820ca9bcdb2c09" } } ], "extra": [ 1, 37, 248, 68, 23, 13, 155, 157, 63, 107, 195, 24, 52, 11, 150, 116, 131, 248, 98, 117, 162, 218, 213, 139, 62, 189, 246, 13, 152, 23, 198, 154, 153, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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