Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34dea8ef0332ff1e82aa27c779e0e8e7a866a9482af2efa8b7de8e5d2984e30b

Tx prefix hash: c8e1572383bdf7615728ba4984916449abb72cb23ddea7930bcf5c63527fdc64
Tx public key: 4a4a761f6b41e9c253dd1e49371d1f6eb067df118a880504050b1ebac44d9d7e
Timestamp: 1714950302 Timestamp [UCT]: 2024-05-05 23:05:02 Age [y:d:h:m:s]: 00:316:04:31:18
Block: 1015694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226014 RingCT/type: yes/0
Extra: 014a4a761f6b41e9c253dd1e49371d1f6eb067df118a880504050b1ebac44d9d7e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0c854e502c9005403fdc56baf7a0383d37d6fe7cfea76f3a32b6e15a9ec48d 0.600000000000 1479133 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": 1015704, "vin": [ { "gen": { "height": 1015694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0c854e502c9005403fdc56baf7a0383d37d6fe7cfea76f3a32b6e15a9ec48d" } } ], "extra": [ 1, 74, 74, 118, 31, 107, 65, 233, 194, 83, 221, 30, 73, 55, 29, 31, 110, 176, 103, 223, 17, 138, 136, 5, 4, 5, 11, 30, 186, 196, 77, 157, 126, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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