Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ebce384648194a4db1b03385b2b99aead0c1dde8ba0ee0c5f264c5721a190e

Tx prefix hash: 6f13690cbbc05202fb61fa8e19254b0de1f967b6dc56fef4c06972bebfd93114
Tx public key: 8b70ff3f0f184c06eb2780b6b6660c6eecf98dc7878f89ce870f9f96203616df
Timestamp: 1745776187 Timestamp [UCT]: 2025-04-27 17:49:47 Age [y:d:h:m:s]: 00:014:18:19:51
Block: 1270738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10560 RingCT/type: yes/0
Extra: 018b70ff3f0f184c06eb2780b6b6660c6eecf98dc7878f89ce870f9f96203616df02110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 822c7a45b3f1e3f16bf682e5341987cbd8939d578f203a6564aacab2ec417d34 0.600000000000 1757983 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": 1270748, "vin": [ { "gen": { "height": 1270738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "822c7a45b3f1e3f16bf682e5341987cbd8939d578f203a6564aacab2ec417d34" } } ], "extra": [ 1, 139, 112, 255, 63, 15, 24, 76, 6, 235, 39, 128, 182, 182, 102, 12, 110, 236, 249, 141, 199, 135, 143, 137, 206, 135, 15, 159, 150, 32, 54, 22, 223, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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