Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66dd3ac1c92b3b92e3b5f69893e13def77f2307b801fd8081a45ead1fab035c0

Tx prefix hash: 54a78c2c4eb06068d039cdf7b6dc94c51d640429d5adf171831097a437ff7310
Tx public key: 2fe39af58233f0cfe39957ff348947f354e6efba666b2bf0e0f239d241ac952b
Timestamp: 1723343032 Timestamp [UCT]: 2024-08-11 02:23:52 Age [y:d:h:m:s]: 00:218:09:58:51
Block: 1085265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156001 RingCT/type: yes/0
Extra: 012fe39af58233f0cfe39957ff348947f354e6efba666b2bf0e0f239d241ac952b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e987c4a187f51884b1453ca34e57703c8e4b5d1ec94d449767aff709a6507c05 0.600000000000 1559814 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": 1085275, "vin": [ { "gen": { "height": 1085265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e987c4a187f51884b1453ca34e57703c8e4b5d1ec94d449767aff709a6507c05" } } ], "extra": [ 1, 47, 227, 154, 245, 130, 51, 240, 207, 227, 153, 87, 255, 52, 137, 71, 243, 84, 230, 239, 186, 102, 107, 43, 240, 224, 242, 57, 210, 65, 172, 149, 43, 2, 17, 0, 0, 0, 3, 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