Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b70591b6caa73776b4185c38406e11b18b2e95157fe59f35ba09ab5eea23a7c4

Tx prefix hash: 7e204f671089c98fb6e8c040179e3453509639a0073a5659aad6212eb0168a0e
Tx public key: 00f522e59c18dfc7285ec74fd50ae657dc5201ac567ec91f51576e19e8982d84
Timestamp: 1718701932 Timestamp [UCT]: 2024-06-18 09:12:12 Age [y:d:h:m:s]: 00:284:00:53:22
Block: 1046800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202962 RingCT/type: yes/0
Extra: 0100f522e59c18dfc7285ec74fd50ae657dc5201ac567ec91f51576e19e8982d840211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4133f3d95aa3a559d1e3a31d1b96c7d7a58f0e3ffecf8ee5c89ce8026c316585 0.600000000000 1516619 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": 1046810, "vin": [ { "gen": { "height": 1046800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4133f3d95aa3a559d1e3a31d1b96c7d7a58f0e3ffecf8ee5c89ce8026c316585" } } ], "extra": [ 1, 0, 245, 34, 229, 156, 24, 223, 199, 40, 94, 199, 79, 213, 10, 230, 87, 220, 82, 1, 172, 86, 126, 201, 31, 81, 87, 110, 25, 232, 152, 45, 132, 2, 17, 0, 0, 0, 3, 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