Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4823d68fa1ba76ee44b848a6c7f04340a18b1d8f6a5539de2a3ed099ca0831b

Tx prefix hash: 882e95991e382a3f518204d08e853e9237a65e378b7e620ffba1901547a58312
Tx public key: 4c0fbf42e7b7e97f7c651c0c38794ce109f16fc23f4dd155f22ba66963e53738
Timestamp: 1714990812 Timestamp [UCT]: 2024-05-06 10:20:12 Age [y:d:h:m:s]: 00:316:04:19:29
Block: 1016028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226026 RingCT/type: yes/0
Extra: 014c0fbf42e7b7e97f7c651c0c38794ce109f16fc23f4dd155f22ba66963e5373802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9083152d9d7e2a016b0cd03d5acfc590b503d9dd50faf185a039c999aea2d4ca 0.600000000000 1479497 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": 1016038, "vin": [ { "gen": { "height": 1016028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9083152d9d7e2a016b0cd03d5acfc590b503d9dd50faf185a039c999aea2d4ca" } } ], "extra": [ 1, 76, 15, 191, 66, 231, 183, 233, 127, 124, 101, 28, 12, 56, 121, 76, 225, 9, 241, 111, 194, 63, 77, 209, 85, 242, 43, 166, 105, 99, 229, 55, 56, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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