Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b5aeb878530238ffabd30a1f093681048cf5ecf5ff2cef68aa33b820276aef

Tx prefix hash: 1094cf974b82f2f22f99546835e584f09b876acb67da20894c6244c38da89b64
Tx public key: 4ea19267c866ddb44aff7913a31ae808bb1b5733d60dd7a736089e5a70060ecc
Timestamp: 1772127493 Timestamp [UTC]: 2026-02-26 17:38:13 Age [y:d:h:m:s]: 00:267:03:16:54
Block: 1486347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196584 RingCT/type: yes/0
Extra: 014ea19267c866ddb44aff7913a31ae808bb1b5733d60dd7a736089e5a70060ecc021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e53333c9a28f4891c306ea62c7d5eafb454fc121bf15a9d6012f12f529c3d5ee 0.000600000000 1975797 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": 1486357, "vin": [ { "gen": { "height": 1486347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e53333c9a28f4891c306ea62c7d5eafb454fc121bf15a9d6012f12f529c3d5ee" } } ], "extra": [ 1, 78, 161, 146, 103, 200, 102, 221, 180, 74, 255, 121, 19, 163, 26, 232, 8, 187, 27, 87, 51, 214, 13, 215, 167, 54, 8, 158, 90, 112, 6, 14, 204, 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: