Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d055d41b15dc11584a8b08e37e824a1f1e942f8ce386daa9a2023f99c0081909

Tx prefix hash: 96c944410a1acd4eeee795d2849f1c2784f467f9da7137416534031fcf433ec1
Tx public key: 7fc844429cb51c7e6021d54ac225726c375c7a1d4a112e26f3f6d1c7affe29c5
Timestamp: 1727544214 Timestamp [UCT]: 2024-09-28 17:23:34 Age [y:d:h:m:s]: 00:195:02:15:56
Block: 1120107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139241 RingCT/type: yes/0
Extra: 017fc844429cb51c7e6021d54ac225726c375c7a1d4a112e26f3f6d1c7affe29c5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7829d8b49263764d6003244d4b31c20101d2c9c9248119e045ed768afa06de6c 0.600000000000 1601904 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": 1120117, "vin": [ { "gen": { "height": 1120107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7829d8b49263764d6003244d4b31c20101d2c9c9248119e045ed768afa06de6c" } } ], "extra": [ 1, 127, 200, 68, 66, 156, 181, 28, 126, 96, 33, 213, 74, 194, 37, 114, 108, 55, 92, 122, 29, 74, 17, 46, 38, 243, 246, 209, 199, 175, 254, 41, 197, 2, 17, 0, 0, 0, 4, 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