Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 094a73c2674cfbe82168301c501b736861c5d5daada7c2ac95ac1bb9b561cb77

Tx prefix hash: ede8e3969fcb3157eb22f2369ef436f792f6f2c256a638b91300bdfb14239e86
Tx public key: 57b1a34af55d69eda77d041ff8b516c25a9401b7c759b95ea8d95b38a58932a4
Timestamp: 1762015695 Timestamp [UCT]: 2025-11-01 16:48:15 Age [y:d:h:m:s]: 00:006:15:08:43
Block: 1402767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4748 RingCT/type: yes/0
Extra: 0157b1a34af55d69eda77d041ff8b516c25a9401b7c759b95ea8d95b38a58932a40211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 797fb3b3b73c4274372c84a2c66cd7d3ed87eabfb8fcb33eb04a58411b9fe4f0 0.600000000000 1891086 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": 1402777, "vin": [ { "gen": { "height": 1402767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "797fb3b3b73c4274372c84a2c66cd7d3ed87eabfb8fcb33eb04a58411b9fe4f0" } } ], "extra": [ 1, 87, 177, 163, 74, 245, 93, 105, 237, 167, 125, 4, 31, 248, 181, 22, 194, 90, 148, 1, 183, 199, 89, 185, 94, 168, 217, 91, 56, 165, 137, 50, 164, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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