Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df470fc6961b8c0faedc3e482e7fbb75bf9c3c08e3569c271ddd239636aa85e

Tx prefix hash: 6fa19ddda2d88246e9c3e83076f48c11fa8bdeb26f0e69adb8b3efa69546a3e1
Tx public key: fbd4be3c9294eb82b0d330a4261427684eb665e55e5c0524e94456d1f990b3e3
Timestamp: 1768685988 Timestamp [UTC]: 2026-01-17 21:39:48 Age [y:d:h:m:s]: 00:302:11:00:46
Block: 1457900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221631 RingCT/type: yes/0
Extra: 01fbd4be3c9294eb82b0d330a4261427684eb665e55e5c0524e94456d1f990b3e3021100000008215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4cd0b8ec8235c5dcbc8960f2d78691b9868cf29b091dc0bf59d84c0d237684f9 0.000600000000 1947036 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 dinastycoin-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": 1457910, "vin": [ { "gen": { "height": 1457900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cd0b8ec8235c5dcbc8960f2d78691b9868cf29b091dc0bf59d84c0d237684f9" } } ], "extra": [ 1, 251, 212, 190, 60, 146, 148, 235, 130, 176, 211, 48, 164, 38, 20, 39, 104, 78, 182, 101, 229, 94, 92, 5, 36, 233, 68, 86, 209, 249, 144, 179, 227, 2, 17, 0, 0, 0, 8, 33, 91, 191, 137, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: