Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee195ebf71108e6d790661ad15e7e1f3a54c5c58b6854a3387daaff75d15eac

Tx prefix hash: 3b94a2727a64d761568b8dee84217811c92d5cc1884444afde731e30fe7b6a98
Tx public key: 97e10e6e1feebfa154f8129a7482194adc3ea9cd7bc919c53696d64e1bf4a084
Timestamp: 1735350024 Timestamp [UCT]: 2024-12-28 01:40:24 Age [y:d:h:m:s]: 00:102:18:41:39
Block: 1184679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73245 RingCT/type: yes/0
Extra: 0197e10e6e1feebfa154f8129a7482194adc3ea9cd7bc919c53696d64e1bf4a0840211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b08e25da7bb6249ab8a2b2d360b31c361b441d6e6dfd00842d7c5e956b146476 0.600000000000 1671138 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": 1184689, "vin": [ { "gen": { "height": 1184679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b08e25da7bb6249ab8a2b2d360b31c361b441d6e6dfd00842d7c5e956b146476" } } ], "extra": [ 1, 151, 225, 14, 110, 31, 238, 191, 161, 84, 248, 18, 154, 116, 130, 25, 74, 220, 62, 169, 205, 123, 201, 25, 197, 54, 150, 214, 78, 27, 244, 160, 132, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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