Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1a95fb1b044cff2b5309f553e8bdbbd3dea11494933d1a582d60d5c0caf9b0

Tx prefix hash: 46ab0eb35dee9cc1ad4a2d84ebd724319ba12d0efae1883f63fb97ed54ae4de0
Tx public key: a5ff8b2cad43c10f38a9571804db50c41b1c09a21c3d4f9a6039d3c48ad31f74
Timestamp: 1774421302 Timestamp [UTC]: 2026-03-25 06:48:22 Age [y:d:h:m:s]: 00:236:17:17:00
Block: 1505331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174680 RingCT/type: yes/0
Extra: 01a5ff8b2cad43c10f38a9571804db50c41b1c09a21c3d4f9a6039d3c48ad31f74021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 54bf4532d62e3b8967e5dc4be497bf2d5bdc53d712603f7da45997830634eb39 0.000600000000 1995063 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": 1505341, "vin": [ { "gen": { "height": 1505331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54bf4532d62e3b8967e5dc4be497bf2d5bdc53d712603f7da45997830634eb39" } } ], "extra": [ 1, 165, 255, 139, 44, 173, 67, 193, 15, 56, 169, 87, 24, 4, 219, 80, 196, 27, 28, 9, 162, 28, 61, 79, 154, 96, 57, 211, 196, 138, 211, 31, 116, 2, 17, 0, 0, 0, 6, 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: