Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fbea25309961beaae3301d8f7b31b7e98836cde87e03838738259ecd5f45196

Tx prefix hash: 73c0a43e0c80cc38d5c751f7a789ff4675211b75c5000bb19a8daff44789d433
Tx public key: e5a68c30465b3e57b8a2a1cca197d7005cfb1d106bedd05df453fe7113fbf3a2
Timestamp: 1581514956 Timestamp [UCT]: 2020-02-12 13:42:36 Age [y:d:h:m:s]: 04:267:15:21:18
Block: 63430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083429 RingCT/type: yes/0
Extra: 01e5a68c30465b3e57b8a2a1cca197d7005cfb1d106bedd05df453fe7113fbf3a202110000000212c4732d000000000000000000

1 output(s) for total of 378.322623552000 dcy

stealth address amount amount idx
00: d530b5002046f28a0f08c8d3cf88f6d1e0511e18f2aa800f98b2f9f9d0849b3d 378.322623552000 116980 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": 63440, "vin": [ { "gen": { "height": 63430 } } ], "vout": [ { "amount": 378322623552, "target": { "key": "d530b5002046f28a0f08c8d3cf88f6d1e0511e18f2aa800f98b2f9f9d0849b3d" } } ], "extra": [ 1, 229, 166, 140, 48, 70, 91, 62, 87, 184, 162, 161, 204, 161, 151, 215, 0, 92, 251, 29, 16, 107, 237, 208, 93, 244, 83, 254, 113, 19, 251, 243, 162, 2, 17, 0, 0, 0, 2, 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