Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38728b11ff88b7746ca3d57df7f237a0a0fcdce2aa28d73f02b8d5b64dde1476

Tx prefix hash: 08a38531c9f680eb1d66cdf23aabee2805a56a4fc74e53ce1aa0bd75bdee023a
Tx public key: 1a6e5ee37d08d315cc692345bb178894b9c7d2fd3a15da9b176acee0ed7f5352
Timestamp: 1771147341 Timestamp [UTC]: 2026-02-15 09:22:21 Age [y:d:h:m:s]: 00:125:09:25:42
Block: 1478237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85820 RingCT/type: yes/0
Extra: 011a6e5ee37d08d315cc692345bb178894b9c7d2fd3a15da9b176acee0ed7f5352021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 264c64c30932d0ffe61dd5779ceac1efe50a99d44d4a5092d9ab4008276df151 0.000600000000 1967565 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": 1478247, "vin": [ { "gen": { "height": 1478237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "264c64c30932d0ffe61dd5779ceac1efe50a99d44d4a5092d9ab4008276df151" } } ], "extra": [ 1, 26, 110, 94, 227, 125, 8, 211, 21, 204, 105, 35, 69, 187, 23, 136, 148, 185, 199, 210, 253, 58, 21, 218, 155, 23, 106, 206, 224, 237, 127, 83, 82, 2, 17, 0, 0, 0, 1, 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: