Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e74574e7b5a26c1094effd08886fea6c141dbe8794567ed4d3d8b754d7cca9e9

Tx prefix hash: 1e21eac7d390ad19e8506c8d460ca6e8d15f297d3c9534efd8086ff30a58a24d
Tx public key: 083c80dbbeaade927a8937e4df60325f9041fe37291ba99eebd1e574a6bce3a2
Timestamp: 1581476589 Timestamp [UCT]: 2020-02-12 03:03:09 Age [y:d:h:m:s]: 05:111:06:38:06
Block: 63277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232266 RingCT/type: yes/0
Extra: 01083c80dbbeaade927a8937e4df60325f9041fe37291ba99eebd1e574a6bce3a202110000000312c4732d000000000000000000

1 output(s) for total of 378.737096120000 dcy

stealth address amount amount idx
00: e2133b3ae1738e8e8270bdca63059d372370d8b3ce349e5ef6273e1cbd2fd035 378.737096120000 116633 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": 63287, "vin": [ { "gen": { "height": 63277 } } ], "vout": [ { "amount": 378737096120, "target": { "key": "e2133b3ae1738e8e8270bdca63059d372370d8b3ce349e5ef6273e1cbd2fd035" } } ], "extra": [ 1, 8, 60, 128, 219, 190, 170, 222, 146, 122, 137, 55, 228, 223, 96, 50, 95, 144, 65, 254, 55, 41, 27, 169, 158, 235, 209, 229, 116, 166, 188, 227, 162, 2, 17, 0, 0, 0, 3, 18, 196, 115, 45, 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