Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dcebc8e6f46f488b907ef1fff25f4a31112b8c0c6661afa6df152d8e7a1ec24

Tx prefix hash: 34040a73e4f983961c34c6695fbb74e9761dcc4396b9a9dfbe55a28bcda3d593
Tx public key: 002b1efe177d49ce54f4bde7ee84cb837f016f4f38f106d09fddd9a52a1d3be5
Timestamp: 1773054292 Timestamp [UTC]: 2026-03-09 11:04:52 Age [y:d:h:m:s]: 00:257:19:00:31
Block: 1494025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189469 RingCT/type: yes/0
Extra: 01002b1efe177d49ce54f4bde7ee84cb837f016f4f38f106d09fddd9a52a1d3be5021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe37d787867c3bdff06900301720167742b976d0b5deedb6ceccb70f7ea0139b 0.000600000000 1983591 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": 1494035, "vin": [ { "gen": { "height": 1494025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe37d787867c3bdff06900301720167742b976d0b5deedb6ceccb70f7ea0139b" } } ], "extra": [ 1, 0, 43, 30, 254, 23, 125, 73, 206, 84, 244, 189, 231, 238, 132, 203, 131, 127, 1, 111, 79, 56, 241, 6, 208, 159, 221, 217, 165, 42, 29, 59, 229, 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: