Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a8cd9fd37f366130e3ec5154c9db3f614e11ae9df93ed9eebaf982a0a1a930

Tx prefix hash: f5430c9e779e0d130b3ed428890b3a2d1bd1a833f00c6bc20b357228496f18f2
Tx public key: a0b29ca27dd0e8ec199113af494f6b048b6a4e85f45540ca75632ad46d20bf5b
Timestamp: 1772000527 Timestamp [UTC]: 2026-02-25 06:22:07 Age [y:d:h:m:s]: 00:268:01:40:36
Block: 1485341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197185 RingCT/type: yes/0
Extra: 01a0b29ca27dd0e8ec199113af494f6b048b6a4e85f45540ca75632ad46d20bf5b021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 422c4224d5b0c56aa402bb42e1117fbc0db3b432d81cdd0dd9851fd90ecaf5ab 0.000600000000 1974775 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": 1485351, "vin": [ { "gen": { "height": 1485341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "422c4224d5b0c56aa402bb42e1117fbc0db3b432d81cdd0dd9851fd90ecaf5ab" } } ], "extra": [ 1, 160, 178, 156, 162, 125, 208, 232, 236, 25, 145, 19, 175, 73, 79, 107, 4, 139, 106, 78, 133, 244, 85, 64, 202, 117, 99, 42, 212, 109, 32, 191, 91, 2, 17, 0, 0, 0, 6, 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: