Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be7f8cc966003a0640ed2f83a182a88b1687d69bbe7bdc9500d83af280d4e1b6

Tx prefix hash: db70bf9b829b8395df74dee56d583a091308eba5b7f81b8df6b9efbce797563c
Tx public key: 5228969c3ee85c672b05ab82b262376a7070772781583582e44e0893d98779aa
Timestamp: 1771791125 Timestamp [UTC]: 2026-02-22 20:12:05 Age [y:d:h:m:s]: 00:269:15:54:39
Block: 1483584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198292 RingCT/type: yes/0
Extra: 015228969c3ee85c672b05ab82b262376a7070772781583582e44e0893d98779aa021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1db0a05e315947b6a09174dd85bfabd8f560caaa7c4f76abc1c79b0a304cf98e 0.000600000000 1972994 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": 1483594, "vin": [ { "gen": { "height": 1483584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db0a05e315947b6a09174dd85bfabd8f560caaa7c4f76abc1c79b0a304cf98e" } } ], "extra": [ 1, 82, 40, 150, 156, 62, 232, 92, 103, 43, 5, 171, 130, 178, 98, 55, 106, 112, 112, 119, 39, 129, 88, 53, 130, 228, 78, 8, 147, 217, 135, 121, 170, 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: