Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7457f0b00598969e73c9fa4a6b4a8c70b5fe115a1d68afab2cce5ac4c04d1106

Tx prefix hash: 44905052764faa43f64a41483a59c2e8f308d91b76eb7da014fde1e39617b6ac
Tx public key: e3186db04fb1fcabddc4b88acf121c14f89b9c9968adbcde77985c08cb559701
Timestamp: 1723792588 Timestamp [UCT]: 2024-08-16 07:16:28 Age [y:d:h:m:s]: 01:084:07:52:54
Block: 1088994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318734 RingCT/type: yes/0
Extra: 01e3186db04fb1fcabddc4b88acf121c14f89b9c9968adbcde77985c08cb559701021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09982ab57447d6afd2dc9ab0c4fa9c7d3a40cc9760ae28fc50a7455d43e0a97f 0.600000000000 1563613 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": 1089004, "vin": [ { "gen": { "height": 1088994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09982ab57447d6afd2dc9ab0c4fa9c7d3a40cc9760ae28fc50a7455d43e0a97f" } } ], "extra": [ 1, 227, 24, 109, 176, 79, 177, 252, 171, 221, 196, 184, 138, 207, 18, 28, 20, 248, 155, 156, 153, 104, 173, 188, 222, 119, 152, 92, 8, 203, 85, 151, 1, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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