Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f03e8b8bd270ee7ee862bb3fdf655a2032a22e360f5572100d725e2122b7789

Tx prefix hash: e873d47b7d6d0cabce771127d57a706d0cfbc9cf59f920685a3dd556e8709cd8
Tx public key: 7a80a1dcd319bd056f6c03e5a05ab54b7e747422a57f0e4f1628aa5dbdf1e62c
Timestamp: 1709908417 Timestamp [UCT]: 2024-03-08 14:33:37 Age [y:d:h:m:s]: 01:085:08:41:14
Block: 973901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322040 RingCT/type: yes/0
Extra: 017a80a1dcd319bd056f6c03e5a05ab54b7e747422a57f0e4f1628aa5dbdf1e62c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c963d0a8ea2eb0287bd48ee2e380b59c7ae57edd027b15206c6dbdd497722183 0.600000000000 1433844 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": 973911, "vin": [ { "gen": { "height": 973901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c963d0a8ea2eb0287bd48ee2e380b59c7ae57edd027b15206c6dbdd497722183" } } ], "extra": [ 1, 122, 128, 161, 220, 211, 25, 189, 5, 111, 108, 3, 229, 160, 90, 181, 75, 126, 116, 116, 34, 165, 127, 14, 79, 22, 40, 170, 93, 189, 241, 230, 44, 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