Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50a20df404905d8f343dd8de4bfcc0dce2284feda7fe373a0943ba6b6d60c4ee

Tx prefix hash: 1863bf8d4c7ae29002c29a98ed75af8351f13b257518b93050edbed190119685
Tx public key: 3124e60699c931b7753af859f76556e9e1ca955e4cd62d26eaa31e2253e9d4d1
Timestamp: 1747320046 Timestamp [UTC]: 2025-05-15 14:40:46 Age [y:d:h:m:s]: 00:360:01:38:39
Block: 1283523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247676 RingCT/type: yes/0
Extra: 013124e60699c931b7753af859f76556e9e1ca955e4cd62d26eaa31e2253e9d4d10211000000099f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c7299f66a1d7cdf7fb20c0dcf1774765aaae13d81ebbf490b3e5bf59bb2bbba2 0.000600000000 1770942 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": 1283533, "vin": [ { "gen": { "height": 1283523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7299f66a1d7cdf7fb20c0dcf1774765aaae13d81ebbf490b3e5bf59bb2bbba2" } } ], "extra": [ 1, 49, 36, 230, 6, 153, 201, 49, 183, 117, 58, 248, 89, 247, 101, 86, 233, 225, 202, 149, 94, 76, 214, 45, 38, 234, 163, 30, 34, 83, 233, 212, 209, 2, 17, 0, 0, 0, 9, 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: