Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f781b4993bd335b191c0b5a192d994bf6497d75a390497d23f247d5fede74c4d

Tx prefix hash: 3126a9bfb3dba68bf52ac9976b7acc1c605981dec17b5c720b20bad0ecbf0431
Tx public key: 1ffbac205ea9b048acfa116ac4e7877edb67379a836488db855818cc2d1d5437
Timestamp: 1772544787 Timestamp [UTC]: 2026-03-03 13:33:07 Age [y:d:h:m:s]: 00:262:14:06:03
Block: 1489810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193328 RingCT/type: yes/0
Extra: 011ffbac205ea9b048acfa116ac4e7877edb67379a836488db855818cc2d1d5437021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: feef852aea093803e1f9a2cfb3df4de6a30eb7cf7db47d2dbe1e6241cf45c4a2 0.000600000000 1979308 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": 1489820, "vin": [ { "gen": { "height": 1489810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feef852aea093803e1f9a2cfb3df4de6a30eb7cf7db47d2dbe1e6241cf45c4a2" } } ], "extra": [ 1, 31, 251, 172, 32, 94, 169, 176, 72, 172, 250, 17, 106, 196, 231, 135, 126, 219, 103, 55, 154, 131, 100, 136, 219, 133, 88, 24, 204, 45, 29, 84, 55, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: