Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02d0b3ffa6f18492edc0b977e02329cff6d5ddff3e36981e3571a1fbde6a09fc

Tx prefix hash: 17fd624c9ff06f17d6507ea4b81446f32e902ca1235a43623a8108eead349cd1
Tx public key: c5922141fdacd5cb41134fe2dd1a6d14b8d8d7f1b73c96421dc681c64b61c4a4
Timestamp: 1578163058 Timestamp [UCT]: 2020-01-04 18:37:38 Age [y:d:h:m:s]: 05:050:20:14:38
Block: 38726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186118 RingCT/type: yes/0
Extra: 01c5922141fdacd5cb41134fe2dd1a6d14b8d8d7f1b73c96421dc681c64b61c4a4021100000023bd0f9f9f000000000000000000

1 output(s) for total of 456.757340490000 dcy

stealth address amount amount idx
00: 281781615a8bb588948d6e4aa82444a65fe794004f151a144d85d9ff4745498e 456.757340490000 66232 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": 38736, "vin": [ { "gen": { "height": 38726 } } ], "vout": [ { "amount": 456757340490, "target": { "key": "281781615a8bb588948d6e4aa82444a65fe794004f151a144d85d9ff4745498e" } } ], "extra": [ 1, 197, 146, 33, 65, 253, 172, 213, 203, 65, 19, 79, 226, 221, 26, 109, 20, 184, 216, 215, 241, 183, 60, 150, 66, 29, 198, 129, 198, 75, 97, 196, 164, 2, 17, 0, 0, 0, 35, 189, 15, 159, 159, 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