Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0460f929616ad2d3225b98e4f968bf35cb3605888010ea2d218e9d016348bd73

Tx prefix hash: 36f91dd94683dcc6f7f5cbd64351620fe041a566ae9977c70910d9d1f2d4d7b4
Tx public key: f2d93ed434fb07c3be38c84c58f70939e5e36db3fb94ff9d9b2fd0db4de2b4e7
Timestamp: 1746971078 Timestamp [UTC]: 2025-05-11 13:44:38 Age [y:d:h:m:s]: 01:007:18:15:35
Block: 1280633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257483 RingCT/type: yes/0
Extra: 01f2d93ed434fb07c3be38c84c58f70939e5e36db3fb94ff9d9b2fd0db4de2b4e70211000000159f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 22f8caf815f0d1981f3cb749d3d3f6773d5b98dde37bc982c7909737bc9db22a 0.000600000000 1768022 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": 1280643, "vin": [ { "gen": { "height": 1280633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22f8caf815f0d1981f3cb749d3d3f6773d5b98dde37bc982c7909737bc9db22a" } } ], "extra": [ 1, 242, 217, 62, 212, 52, 251, 7, 195, 190, 56, 200, 76, 88, 247, 9, 57, 229, 227, 109, 179, 251, 148, 255, 157, 155, 47, 208, 219, 77, 226, 180, 231, 2, 17, 0, 0, 0, 21, 159, 159, 230, 140, 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: