Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a32e6b69ca1de1a8a4c5ca262991c70480957eed6de54436db906857001728f

Tx prefix hash: a4463c571bc6371716f6b4c1feb932d1adea635078a2d0d80881becd3f55ba30
Tx public key: 606b8f03bdbe197dfd6fc487f1f06597335944ee3cbc3b7adc139cae0cd2ab6e
Timestamp: 1722039264 Timestamp [UCT]: 2024-07-27 00:14:24 Age [y:d:h:m:s]: 00:241:09:40:44
Block: 1074456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172437 RingCT/type: yes/0
Extra: 01606b8f03bdbe197dfd6fc487f1f06597335944ee3cbc3b7adc139cae0cd2ab6e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 385237b8f99702d76b104b33eae0c9c1efe8a88aec2d9a186f2eff8cdf20740f 0.600000000000 1546969 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": 1074466, "vin": [ { "gen": { "height": 1074456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "385237b8f99702d76b104b33eae0c9c1efe8a88aec2d9a186f2eff8cdf20740f" } } ], "extra": [ 1, 96, 107, 143, 3, 189, 190, 25, 125, 253, 111, 196, 135, 241, 240, 101, 151, 51, 89, 68, 238, 60, 188, 59, 122, 220, 19, 156, 174, 12, 210, 171, 110, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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