Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b74845e63c63823cfa2aebc3c1f19c4f1d6512ede0804ed1a8bdf325d39a8ac

Tx prefix hash: b57e1f575b5ae282461a164bd2a84c5b696d024b48c36dada2dc762934c875d5
Tx public key: c9f169127dfe271afe6ad56bc1d5f55e97c878fa7fe44b285af479029a0566d7
Timestamp: 1728215682 Timestamp [UCT]: 2024-10-06 11:54:42 Age [y:d:h:m:s]: 00:091:21:16:16
Block: 1125671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65693 RingCT/type: yes/0
Extra: 01c9f169127dfe271afe6ad56bc1d5f55e97c878fa7fe44b285af479029a0566d702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 004f382744387e9fd35108fdb90e118b4069ba3fd978f46b26e565dd5722e9e4 0.600000000000 1608422 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": 1125681, "vin": [ { "gen": { "height": 1125671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "004f382744387e9fd35108fdb90e118b4069ba3fd978f46b26e565dd5722e9e4" } } ], "extra": [ 1, 201, 241, 105, 18, 125, 254, 39, 26, 254, 106, 213, 107, 193, 213, 245, 94, 151, 200, 120, 250, 127, 228, 75, 40, 90, 244, 121, 2, 154, 5, 102, 215, 2, 17, 0, 0, 0, 2, 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