Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9b1f76113bf3eeb15e33945d04e9e99076bc0fdea3b84e8be98af9ce175b5be

Tx prefix hash: c1d31958577fbe74e8f16693e4e89c60da738ee0d8a345515d896f82623a84a2
Tx public key: 1b58c0361fc8ddb7913aefc9bf40695d78d234e6954ab5c49895eedc7126ffc5
Timestamp: 1715066904 Timestamp [UCT]: 2024-05-07 07:28:24 Age [y:d:h:m:s]: 00:325:11:30:01
Block: 1016666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232647 RingCT/type: yes/0
Extra: 011b58c0361fc8ddb7913aefc9bf40695d78d234e6954ab5c49895eedc7126ffc50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d9d04f5d754879eca6a78ca7f914f181047397e25fc083c381e71bfbe6d2b4 0.600000000000 1480315 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": 1016676, "vin": [ { "gen": { "height": 1016666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d9d04f5d754879eca6a78ca7f914f181047397e25fc083c381e71bfbe6d2b4" } } ], "extra": [ 1, 27, 88, 192, 54, 31, 200, 221, 183, 145, 58, 239, 201, 191, 64, 105, 93, 120, 210, 52, 230, 149, 74, 181, 196, 152, 149, 238, 220, 113, 38, 255, 197, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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