Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37c2104f03b1d6cd56a8eaebc2f53c14f3167b78cc94ce9655dc01e493575d75

Tx prefix hash: 232a48332a84238faedcfccf36f34e4f807f1d7985a8375cfd10c65f05dd9c3e
Tx public key: 0f940d2592b39e850c7dce2e189a50cb59cca385342c268824fbfa600ca7bd80
Timestamp: 1694439311 Timestamp [UCT]: 2023-09-11 13:35:11 Age [y:d:h:m:s]: 01:209:13:54:26
Block: 845833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410870 RingCT/type: yes/0
Extra: 010f940d2592b39e850c7dce2e189a50cb59cca385342c268824fbfa600ca7bd8002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.966950432000 dcy

stealth address amount amount idx
00: 675ca35b4ee517a11f92e323699837761aaaf4a7b0825f91375b3f0a0333e4e0 0.966950432000 1299253 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": 845843, "vin": [ { "gen": { "height": 845833 } } ], "vout": [ { "amount": 966950432, "target": { "key": "675ca35b4ee517a11f92e323699837761aaaf4a7b0825f91375b3f0a0333e4e0" } } ], "extra": [ 1, 15, 148, 13, 37, 146, 179, 158, 133, 12, 125, 206, 46, 24, 154, 80, 203, 89, 204, 163, 133, 52, 44, 38, 136, 36, 251, 250, 96, 12, 167, 189, 128, 2, 17, 0, 0, 0, 4, 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