Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b845cca34ce0cef348d1842879f1678cdeaeb7c5ca9c02fc8c5882901a1e8ba3

Tx prefix hash: ada50783c50b7a8eea92b0898c43f32d931b2dcc7d7c5972dd6854bb1e1ca066
Tx public key: d01fbc6d4cd5f45eecf37d7bdc068d312bc40f25581ed44f68adf1f41d1f28ee
Timestamp: 1733998073 Timestamp [UCT]: 2024-12-12 10:07:53 Age [y:d:h:m:s]: 00:097:03:40:58
Block: 1173523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69221 RingCT/type: yes/0
Extra: 01d01fbc6d4cd5f45eecf37d7bdc068d312bc40f25581ed44f68adf1f41d1f28ee0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea5783516b564b78691de66dc7bcef436b3fc02a86fa0f4599c66daa363a2b93 0.600000000000 1659556 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": 1173533, "vin": [ { "gen": { "height": 1173523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea5783516b564b78691de66dc7bcef436b3fc02a86fa0f4599c66daa363a2b93" } } ], "extra": [ 1, 208, 31, 188, 109, 76, 213, 244, 94, 236, 243, 125, 123, 220, 6, 141, 49, 43, 196, 15, 37, 88, 30, 212, 79, 104, 173, 241, 244, 29, 31, 40, 238, 2, 17, 0, 0, 0, 7, 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