Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70cdd2277d4d1955381d644156ae51b2aeacc8f6c202dea761820e64c0093113

Tx prefix hash: 68516d01c33c544c11b8b8287f4f0bd40d9c056d3bb000ddf2c975ff4b9a77be
Tx public key: a7a8f3f95702a9528d17d6aef518e67aea31a338787deff25f049fd424477788
Timestamp: 1699831397 Timestamp [UCT]: 2023-11-12 23:23:17 Age [y:d:h:m:s]: 02:011:18:39:04
Block: 890360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528198 RingCT/type: yes/0
Extra: 01a7a8f3f95702a9528d17d6aef518e67aea31a338787deff25f049fd42447778802110000000133af99f4000000000000000000

1 output(s) for total of 0.688442561000 dcy

stealth address amount amount idx
00: ef5b87b7ba31d493f02e641049731c89989d901dc66e2477909efdf2cb029897 0.688442561000 1346383 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": 890370, "vin": [ { "gen": { "height": 890360 } } ], "vout": [ { "amount": 688442561, "target": { "key": "ef5b87b7ba31d493f02e641049731c89989d901dc66e2477909efdf2cb029897" } } ], "extra": [ 1, 167, 168, 243, 249, 87, 2, 169, 82, 141, 23, 214, 174, 245, 24, 230, 122, 234, 49, 163, 56, 120, 125, 239, 242, 95, 4, 159, 212, 36, 71, 119, 136, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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