Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab21199b0d33f912354efcbfbb21fb9a09ab5ce418f3a4cf4bfc9bf63a01e0ac

Tx prefix hash: ae2d518abec1dce9319a7e983b5ec4b374ecf516f95bbb750b7904a973b1399a
Tx public key: c8460ca3c3af2b1054e5f09879e0b3108009d8c550cf5622b938eea0d8841cd0
Timestamp: 1708676508 Timestamp [UCT]: 2024-02-23 08:21:48 Age [y:d:h:m:s]: 01:031:22:03:35
Block: 963678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283816 RingCT/type: yes/0
Extra: 01c8460ca3c3af2b1054e5f09879e0b3108009d8c550cf5622b938eea0d8841cd002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe639607b80f477de9fda570ffe6d79dc3fbb495ac9f84a6c852c3ebb81fb02 0.600000000000 1423397 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": 963688, "vin": [ { "gen": { "height": 963678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe639607b80f477de9fda570ffe6d79dc3fbb495ac9f84a6c852c3ebb81fb02" } } ], "extra": [ 1, 200, 70, 12, 163, 195, 175, 43, 16, 84, 229, 240, 152, 121, 224, 179, 16, 128, 9, 216, 197, 80, 207, 86, 34, 185, 56, 238, 160, 216, 132, 28, 208, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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