Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dfd64459a122b943031f4ac9bb3957a6274e52cd9aaa5bce35d0e4a8707019c

Tx prefix hash: 1a01c46560e981efa8a1c5eba9a48396cf4992592d845093ec21dea53483a5dc
Tx public key: fcaa0d6b4203374c8107b2a5a9a5ca912868b83b67dbd1a0e0019da258f12ff2
Timestamp: 1750974927 Timestamp [UCT]: 2025-06-26 21:55:27 Age [y:d:h:m:s]: 00:140:14:43:06
Block: 1313430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98521 RingCT/type: yes/0
Extra: 01fcaa0d6b4203374c8107b2a5a9a5ca912868b83b67dbd1a0e0019da258f12ff202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79d245439eb0784f30c3f73c783ad3949450eaf5c6372884ba4d64aab3d43f80 0.600000000000 1801071 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": 1313440, "vin": [ { "gen": { "height": 1313430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79d245439eb0784f30c3f73c783ad3949450eaf5c6372884ba4d64aab3d43f80" } } ], "extra": [ 1, 252, 170, 13, 107, 66, 3, 55, 76, 129, 7, 178, 165, 169, 165, 202, 145, 40, 104, 184, 59, 103, 219, 209, 160, 224, 1, 157, 162, 88, 241, 47, 242, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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