Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8e9863eeb7d68e82b934b3db03b09b53553679eef26fc9096c64e0f1cb153f1

Tx prefix hash: d3df11b94a269625470c11b7e5dac51ae50b861810b172e3ab7d93b5b1d5ad0d
Tx public key: 84f18af89a2306f8e64bf5ab24385f006c4f6b6878ddb6bd3abe308810d9a130
Timestamp: 1732877754 Timestamp [UCT]: 2024-11-29 10:55:54 Age [y:d:h:m:s]: 00:200:06:29:09
Block: 1164219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142882 RingCT/type: yes/0
Extra: 0184f18af89a2306f8e64bf5ab24385f006c4f6b6878ddb6bd3abe308810d9a130021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1326715a83e982bd7587d87cfaf3da9f26889cfa12b13a20677cad9eefe93bd 0.600000000000 1649892 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": 1164229, "vin": [ { "gen": { "height": 1164219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1326715a83e982bd7587d87cfaf3da9f26889cfa12b13a20677cad9eefe93bd" } } ], "extra": [ 1, 132, 241, 138, 248, 154, 35, 6, 248, 230, 75, 245, 171, 36, 56, 95, 0, 108, 79, 107, 104, 120, 221, 182, 189, 58, 190, 48, 136, 16, 217, 161, 48, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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