Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b95e7e4d435fc7c8450f92bdcc7793c04ec4b738e4b67133d2968e8c1e534b6e

Tx prefix hash: 19bfbfbd3ec6de4014e5be8b7d436bed1ffa06aa0095b2d7d604876bfe729c38
Tx public key: ea2234f35eab3fbfb0b26ecf099dd74043802832e4c3e1bc27cd9fa5bf9d5ae6
Timestamp: 1770657933 Timestamp [UTC]: 2026-02-09 17:25:33 Age [y:d:h:m:s]: 00:007:08:17:37
Block: 1474218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 5215 RingCT/type: yes/0
Extra: 01ea2234f35eab3fbfb0b26ecf099dd74043802832e4c3e1bc27cd9fa5bf9d5ae60208e5dd6c1fb21155f5

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3bcf8a54e340cc3363e3f5071b3ec8bb46a5280c92752e88aa1e6b37b19768e1 0.000600000000 1963514 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": 1474228, "vin": [ { "gen": { "height": 1474218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bcf8a54e340cc3363e3f5071b3ec8bb46a5280c92752e88aa1e6b37b19768e1" } } ], "extra": [ 1, 234, 34, 52, 243, 94, 171, 63, 191, 176, 178, 110, 207, 9, 157, 215, 64, 67, 128, 40, 50, 228, 195, 225, 188, 39, 205, 159, 165, 191, 157, 90, 230, 2, 8, 229, 221, 108, 31, 178, 17, 85, 245 ], "rct_signatures": { "type": 0 } }


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