Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38465529ef4f7c4805e2fcb73b83ce636c643abb18a5d260e39445a2e90acfc6

Tx prefix hash: 3dee4a95e841ead5fddd7495cef88d46b941e34094a3f154d616fccb701e5a15
Tx public key: cae047d49a7f91ae5cf98f58c5b80f4415675abe6711eb9cb4b71423bfd248f5
Timestamp: 1785403236 Timestamp [UTC]: 2026-07-30 09:20:36 Age [y:d:h:m:s]: 00:106:12:16:46
Block: 1601661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 76014 RingCT/type: yes/0
Extra: 01cae047d49a7f91ae5cf98f58c5b80f4415675abe6711eb9cb4b71423bfd248f5020857963ec8990a45de

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f90cc348eeaf65bbca4d12618950e72bd2da4d6e9287e519d4af950c6650a1aa 0.000600000000 2091679 of 15 <24>

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": 1601671, "vin": [ { "gen": { "height": 1601661 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f90cc348eeaf65bbca4d12618950e72bd2da4d6e9287e519d4af950c6650a1aa", "view_tag": "24" } } } ], "extra": [ 1, 202, 224, 71, 212, 154, 127, 145, 174, 92, 249, 143, 88, 197, 184, 15, 68, 21, 103, 90, 190, 103, 17, 235, 156, 180, 183, 20, 35, 191, 210, 72, 245, 2, 8, 87, 150, 62, 200, 153, 10, 69, 222 ], "rct_signatures": { "type": 0 } }


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