Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aecfb23a3774ed9931eb64db809640be2d6fb36520887887e00a0df05965efdd

Tx prefix hash: af99eb73204d8cf4e438ea063ff4a7a90a2bad11cd8c756261df070650bba4a1
Tx public key: bf110d3f179bd2559d5962d69372ae93968b5bf9f4d017436d62029a790fa832
Timestamp: 1768323948 Timestamp [UTC]: 2026-01-13 17:05:48 Age [y:d:h:m:s]: 00:309:08:09:45
Block: 1454896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226633 RingCT/type: yes/0
Extra: 01bf110d3f179bd2559d5962d69372ae93968b5bf9f4d017436d62029a790fa832021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3ec60cb3eab2cb33d05ee70131f2f7f7f65c68dc205b906c906edb1666baf6b7 0.000600000000 1943990 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": 1454906, "vin": [ { "gen": { "height": 1454896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ec60cb3eab2cb33d05ee70131f2f7f7f65c68dc205b906c906edb1666baf6b7" } } ], "extra": [ 1, 191, 17, 13, 63, 23, 155, 210, 85, 157, 89, 98, 214, 147, 114, 174, 147, 150, 139, 91, 249, 244, 208, 23, 67, 109, 98, 2, 154, 121, 15, 168, 50, 2, 17, 0, 0, 0, 1, 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: