Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 005fa7feb75724361d05c83984b6d73a56ab340b06fb02a60c1befb7fa955f6d

Tx prefix hash: 88d4889409cce821e88c596976bf812644069cb6a4d68928aa652e4cff9175ef
Tx public key: d11dfa111877583f7af492a572192e0a6f4e75934ceea97e5896be0aa145c828
Timestamp: 1757084490 Timestamp [UTC]: 2025-09-05 15:01:30 Age [y:d:h:m:s]: 01:076:08:28:26
Block: 1361979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321029 RingCT/type: yes/0
Extra: 01d11dfa111877583f7af492a572192e0a6f4e75934ceea97e5896be0aa145c828021100000005dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd1a19998ffff0e33930c86be8dc63b0ed78750cf7d7234eebe7477f6ce56af2 0.000600000000 1850002 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": 1361989, "vin": [ { "gen": { "height": 1361979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd1a19998ffff0e33930c86be8dc63b0ed78750cf7d7234eebe7477f6ce56af2" } } ], "extra": [ 1, 209, 29, 250, 17, 24, 119, 88, 63, 122, 244, 146, 165, 114, 25, 46, 10, 111, 78, 117, 147, 76, 238, 169, 126, 88, 150, 190, 10, 161, 69, 200, 40, 2, 17, 0, 0, 0, 5, 223, 195, 186, 73, 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: