Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2b97e2c8555cd66463bab211b9b7cfd5011b4302c4cf0ccb5a5a9b8f4aacfa5

Tx prefix hash: ff33161ab86a3f37c92ff9d7bc18de29679b18921cdf9d8e984b7384dd46e9f8
Tx public key: fc0b6af11572b578e48a8539896b149ce5e4cc6fc7427aa13b074475405b5540
Timestamp: 1774740365 Timestamp [UTC]: 2026-03-28 23:26:05 Age [y:d:h:m:s]: 00:233:06:08:41
Block: 1507969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172201 RingCT/type: yes/0
Extra: 01fc0b6af11572b578e48a8539896b149ce5e4cc6fc7427aa13b074475405b5540021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3572ef64c1d6568ae9c62a9c725ef02ccbb53a7565759a6970527542b52a1b92 0.000600000000 1997721 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": 1507979, "vin": [ { "gen": { "height": 1507969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3572ef64c1d6568ae9c62a9c725ef02ccbb53a7565759a6970527542b52a1b92" } } ], "extra": [ 1, 252, 11, 106, 241, 21, 114, 181, 120, 228, 138, 133, 57, 137, 107, 20, 156, 229, 228, 204, 111, 199, 66, 122, 161, 59, 7, 68, 117, 64, 91, 85, 64, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: