Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daf1c2633c41c5240d519e2834536d908d2ea7e5e8411a1470f8c4fbecefc0cc

Tx prefix hash: b0c863fdcf0e6b6476830227682ce32417e94f1587cd6a63ae3b6cbfa7759ffe
Tx public key: 54b812bde52f08376287dd94c37552fbb2b34f667310886ce1e42740b0eabfe9
Timestamp: 1692700275 Timestamp [UCT]: 2023-08-22 10:31:15 Age [y:d:h:m:s]: 01:277:13:26:21
Block: 831395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459567 RingCT/type: yes/0
Extra: 0154b812bde52f08376287dd94c37552fbb2b34f667310886ce1e42740b0eabfe902110000001575e3f0e9000000000000000000

1 output(s) for total of 1.079551389000 dcy

stealth address amount amount idx
00: 4bc5b79f3a5e5fb5e82c44595e78271e0927151d6e486edbd8838dab0e460fc5 1.079551389000 1283817 of 0

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": 831405, "vin": [ { "gen": { "height": 831395 } } ], "vout": [ { "amount": 1079551389, "target": { "key": "4bc5b79f3a5e5fb5e82c44595e78271e0927151d6e486edbd8838dab0e460fc5" } } ], "extra": [ 1, 84, 184, 18, 189, 229, 47, 8, 55, 98, 135, 221, 148, 195, 117, 82, 251, 178, 179, 79, 102, 115, 16, 136, 108, 225, 228, 39, 64, 176, 234, 191, 233, 2, 17, 0, 0, 0, 21, 117, 227, 240, 233, 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