Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443bca57e3854df58444c9f81802923b76920d697f99cb6ce3e585b5dab30705

Tx prefix hash: 44b68f86e3178938133eefa1d8dadcc34286cf71d10391e03e061059c26c0932
Tx public key: 23515aeddc81d7eb3d81db1fba991166a1177fdfb70ccba017545f4a7fd7c5cb
Timestamp: 1721594532 Timestamp [UCT]: 2024-07-21 20:42:12 Age [y:d:h:m:s]: 00:256:00:22:18
Block: 1070761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182897 RingCT/type: yes/0
Extra: 0123515aeddc81d7eb3d81db1fba991166a1177fdfb70ccba017545f4a7fd7c5cb02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d76a836999ecfcf9745b32b7ccbab33ca87b3d6f7f02da5e1c23631e951d703b 0.600000000000 1542730 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": 1070771, "vin": [ { "gen": { "height": 1070761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d76a836999ecfcf9745b32b7ccbab33ca87b3d6f7f02da5e1c23631e951d703b" } } ], "extra": [ 1, 35, 81, 90, 237, 220, 129, 215, 235, 61, 129, 219, 31, 186, 153, 17, 102, 161, 23, 127, 223, 183, 12, 203, 160, 23, 84, 95, 74, 127, 215, 197, 203, 2, 17, 0, 0, 0, 12, 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