Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e474f65c6a5d68f4244635bf8e4ddba37804768af8dd5145cb1571617f17515f

Tx prefix hash: 596a6d670aabd953f766156acc6302e3c02b28bb7ed944af2030c0b6f9a01d9a
Tx public key: 80cec142bbf8a644d1874195e7b316987edf9d809b9b798aa75d60fb1af7b5a6
Timestamp: 1710820148 Timestamp [UCT]: 2024-03-19 03:49:08 Age [y:d:h:m:s]: 01:057:21:04:48
Block: 981464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302352 RingCT/type: yes/0
Extra: 0180cec142bbf8a644d1874195e7b316987edf9d809b9b798aa75d60fb1af7b5a60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaf3456c497adec9b208808a59ac6dac2b8b6fa67e49119af15ee60a308ec97f 0.600000000000 1441561 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": 981474, "vin": [ { "gen": { "height": 981464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaf3456c497adec9b208808a59ac6dac2b8b6fa67e49119af15ee60a308ec97f" } } ], "extra": [ 1, 128, 206, 193, 66, 187, 248, 166, 68, 209, 135, 65, 149, 231, 179, 22, 152, 126, 223, 157, 128, 155, 155, 121, 138, 167, 93, 96, 251, 26, 247, 181, 166, 2, 17, 0, 0, 0, 1, 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