Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fe29ce7baf3ca19c24581d3d2143eab675b3b5e63ee06fd9a1614941d46e2e3

Tx prefix hash: d89b4cb1d2134e1b5b61fe55f9e53a56ed16642ea31303509551a35a4a1a86b8
Tx public key: d0dc22f973ad0b6e87e64fa64293f371e26fd544b49a28c0b510e509809abb95
Timestamp: 1723957595 Timestamp [UCT]: 2024-08-18 05:06:35 Age [y:d:h:m:s]: 00:098:13:57:01
Block: 1090375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70507 RingCT/type: yes/0
Extra: 01d0dc22f973ad0b6e87e64fa64293f371e26fd544b49a28c0b510e509809abb9502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea4060b3891b140cc512749b38435187f3fdc97d15d9c484087441acf154b88 0.600000000000 1564998 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": 1090385, "vin": [ { "gen": { "height": 1090375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea4060b3891b140cc512749b38435187f3fdc97d15d9c484087441acf154b88" } } ], "extra": [ 1, 208, 220, 34, 249, 115, 173, 11, 110, 135, 230, 79, 166, 66, 147, 243, 113, 226, 111, 213, 68, 180, 154, 40, 192, 181, 16, 229, 9, 128, 154, 187, 149, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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