Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4f4bc81d812d4677e6dd2fe09c4cf6f449bbbf5775cae0504862aecbd9fbaa8

Tx prefix hash: 81da5c7108860aee7ebc7859132cde27d6bbb6692e808bb52c69505ebea4779d
Tx public key: 273320e91f1b2fc84d1c318912da196eb6291d5cf0bd38f0831920f588e3ba21
Timestamp: 1772225045 Timestamp [UTC]: 2026-02-27 20:44:05 Age [y:d:h:m:s]: 00:266:10:43:00
Block: 1487157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196096 RingCT/type: yes/0
Extra: 01273320e91f1b2fc84d1c318912da196eb6291d5cf0bd38f0831920f588e3ba2102110000001af188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ea173e688fda7316f5ce22c20b19820f801f8637ede896fdbd1cb5bf4c67cbee 0.000600000000 1976621 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": 1487167, "vin": [ { "gen": { "height": 1487157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea173e688fda7316f5ce22c20b19820f801f8637ede896fdbd1cb5bf4c67cbee" } } ], "extra": [ 1, 39, 51, 32, 233, 31, 27, 47, 200, 77, 28, 49, 137, 18, 218, 25, 110, 182, 41, 29, 92, 240, 189, 56, 240, 131, 25, 32, 245, 136, 227, 186, 33, 2, 17, 0, 0, 0, 26, 241, 136, 200, 168, 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: